From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Cc: Georgy Yakovlev <gyakovlev@gentoo.org>
Subject: [gentoo-catalyst] [PATCH 1/3] arch/ppc.toml: add CHOST based subarches
Date: Tue, 20 Oct 2020 21:33:45 -0700 [thread overview]
Message-ID: <20201021043347.632763-1-gyakovlev@gentoo.org> (raw)
if stage spec sets chost value, code in
catalyst/base/stagebase.py#L76 will derive subarch
value from the frontmost part of CHOST triple.
if such subarch is not defined in toml file, build will fail.
Add generic copy of base subarches defined in CHOST format.
Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org>
---
arch/ppc.toml | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/arch/ppc.toml b/arch/ppc.toml
index a3db919e..870c7647 100644
--- a/arch/ppc.toml
+++ b/arch/ppc.toml
@@ -46,10 +46,18 @@ USE = [ "altivec", "ibm",]
COMMON_FLAGS = "-O2 -pipe"
CHOST = "powerpc64-unknown-linux-gnu"
+[ppc64.powerpc64]
+COMMON_FLAGS = "-O2 -pipe"
+CHOST = "powerpc64-unknown-linux-gnu"
+
[ppc64.ppc64le]
COMMON_FLAGS = "-O2 -pipe"
CHOST = "powerpc64le-unknown-linux-gnu"
+[ppc64.powerpc64le]
+COMMON_FLAGS = "-O2 -pipe"
+CHOST = "powerpc64le-unknown-linux-gnu"
+
[ppc.g3]
CHOST = "powerpc-unknown-linux-gnu"
COMMON_FLAGS = "-O2 -mcpu=G3 -mtune=G3 -pipe"
@@ -68,3 +76,6 @@ USE = [ "altivec",]
CHOST = "powerpc-unknown-linux-gnu"
COMMON_FLAGS = "-O2 -mcpu=powerpc -mtune=powerpc -pipe"
+[ppc.powerpc]
+CHOST = "powerpc-unknown-linux-gnu"
+COMMON_FLAGS = "-O2 -mcpu=powerpc -mtune=powerpc -pipe"
--
2.29.0
next reply other threads:[~2020-10-21 4:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 4:33 Georgy Yakovlev [this message]
2020-10-21 4:33 ` [gentoo-catalyst] [PATCH 2/3] arch/ppc.toml: don't force -mabi=elfv2 on power subarches Georgy Yakovlev
2020-10-21 4:33 ` [gentoo-catalyst] [PATCH 3/3] arch/ppc.toml: add power9 subarches Georgy Yakovlev
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=20201021043347.632763-1-gyakovlev@gentoo.org \
--to=gyakovlev@gentoo.org \
--cc=gentoo-catalyst@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