From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: cnf/, /
Date: Fri, 9 Feb 2024 07:26:34 +0000 (UTC) [thread overview]
Message-ID: <1707463592.914d21b02b2b9bc5c8f32284e069685ba62432fd.sam@gentoo> (raw)
commit: 914d21b02b2b9bc5c8f32284e069685ba62432fd
Author: Matoro Mahri <matoro_gentoo <AT> matoro <DOT> tk>
AuthorDate: Sun Oct 29 21:22:44 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Feb 9 07:26:32 2024 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=914d21b0
cnf: add arch-specific configuration example for arc
Signed-off-by: Matoro Mahri <matoro_gentoo <AT> matoro.tk>
Signed-off-by: Sam James <sam <AT> gentoo.org>
NEWS | 6 ++++++
cnf/make.conf.example.arc.diff | 46 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 52 insertions(+)
diff --git a/NEWS b/NEWS
index 0bb525a629..220a0f4f7e 100644
--- a/NEWS
+++ b/NEWS
@@ -6,6 +6,12 @@ Release notes take the form of the following optional categories:
* Bug fixes
* Cleanups
+portage-3.0.62 (UNRELEASED)
+--------------
+
+Features:
+* cnf: make.conf.example.arc: add for the arc arch.
+
portage-3.0.61 (2024-01-05)
--------------
diff --git a/cnf/make.conf.example.arc.diff b/cnf/make.conf.example.arc.diff
new file mode 100644
index 0000000000..4775cb3634
--- /dev/null
+++ b/cnf/make.conf.example.arc.diff
@@ -0,0 +1,46 @@
+--- make.conf.example
++++ make.conf.example
+@@ -22,6 +22,15 @@
+ # Example:
+ #USE="X gtk gnome -alsa"
+
++# Host Setting
++# ============
++#
++# 32-bit ARC systems should use this host setting:
++CHOST="arc-snps-linux-gnu"
++
++# 64-bit ARCv3 and above systems may use this host setting:
++#CHOST="arc64-snps-linux-gnu"
++
+ # Host and optimization settings
+ # ==============================
+ #
+@@ -39,7 +48,17 @@
+ # -frecord-gcc-switches, since otherwise the check could result in false
+ # positive results.
+ #
+-# Please refer to the GCC manual for a list of possible values.
++# -mcpu=<cpu-type> compiles code that runs exclusively on a particular CPU.
++#
++# -mtune=<cpu-series> compiles code that is optimized for a particular CPU, but
++# will run on the CPU specified in -mcpu, or all ARC CPUs if -mcpu= is not
++# specified.
++#
++# -mfpu=<fpu> specifies the capabilities of the FPU to generate floating-point
++# instructions for.
++#
++# Please refer to the "ARC Options" section of the GCC manual for a list of
++# possible CPU and FPU values.
+ #
+ #CFLAGS="-O2 -pipe"
+ #
+@@ -76,7 +95,7 @@
+ # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
+ # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
+ #
+-#ACCEPT_KEYWORDS="~arch"
++#ACCEPT_KEYWORDS="~arc"
+
+ # ACCEPT_LICENSE is used to mask packages based on licensing restrictions.
+ # It may contain both license and group names, where group names are
next reply other threads:[~2024-02-09 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 7:26 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-18 16:45 [gentoo-commits] proj/portage:master commit in: cnf/, / Mike Gilbert
2024-07-21 9:06 Sam James
2024-03-08 16:11 Zac Medico
2023-09-19 7:18 Sam James
2022-12-10 1:47 Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1707463592.914d21b02b2b9bc5c8f32284e069685ba62432fd.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox