public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst][PATCH v1] arch/powerpc.py:add support for subarch power8 bug#560818
Date: Mon, 21 Sep 2015 13:15:42 -0400	[thread overview]
Message-ID: <56003B3E.2060001@gentoo.org> (raw)
In-Reply-To: <56000DEA.6050607@gentoo.org>

On 9/21/15 10:02 AM, Rick "Zero_Chaos" Farina wrote:
> On 09/21/2015 08:38 AM, Leno Hou wrote:
>
> I see no issues here, but I defer to PPC team.
>
> -Zero_Chaos
>
>> Currently catalyst does not support ppc64le arch, we add
>> subarch power8 to support ppc64le and make stage files.
>>
>> Signed-off-by: Leno Hou <lenohou@gmail.com>
>> ---
>>   catalyst/arch/powerpc.py | 11 ++++++++++-
>>   1 file changed, 10 insertions(+), 1 deletion(-)
>>
>> diff --git a/catalyst/arch/powerpc.py b/catalyst/arch/powerpc.py
>> index f903b38..49bdd92 100644
>> --- a/catalyst/arch/powerpc.py
>> +++ b/catalyst/arch/powerpc.py
>> @@ -108,6 +108,14 @@ class arch_power6(arch_ppc64):
>>   		self.settings["CFLAGS"]="-O2 -pipe -mcpu=power6 -mtune=power6"
>>   		self.settings["HOSTUSE"]=["altivec","ibm"]
>>   
>> +class arch_power8(arch_ppc64):
>> +	"builder class for power8 under ppc64le"
>> +	def __init__(self,myspec):
>> +		arch_ppc64.__init__(self,myspec)
>> +		self.settings["CFLAGS"]="-O2 -pipe -mcpu=power8 -mtune=power8 -mabi=elfv2"
>> +		self.settings["CHOST"]="powerpc64le-linux-gnu"
>> +		self.settings["HOSTUSE"]=["altivec","ibm"]
>> +
>>   def register():
>>   	"Inform main catalyst program of the contents of this plugin."
>>   	return ({
>> @@ -122,6 +130,7 @@ def register():
>>   		"power4"	: arch_power4,
>>   		"power5"	: arch_power5,
>>   		"power6"	: arch_power6,
>> +		"power8"	: arch_power8,
>>   		"ppc"		: arch_ppc,
>>   		"ppc64"		: arch_ppc64
>> -	}, ("ppc","ppc64","powerpc","powerpc64"))
>> +	}, ("ppc","ppc64","ppc64le","powerpc","powerpc64","powerpc64le"))
>>

The CHOST is incorrect.  It should powerpc64le-unknown-linux-gnu. Leno, 
can you please try to switch it to that and do another catalyst run.  
You can begin with your current stage3 with the above CHOST and it 
should work out correctly to the new CHOST name.  In another place you 
said there is no compiler "powerpc64le-unknown-linux-gnu" but that makes 
no sense.  The tuple is parsed by gnuconfig script and it should work 
like all other CHOST names we have in gentoo.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



  reply	other threads:[~2015-09-21 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 12:38 [gentoo-catalyst][PATCH v1] arch/powerpc.py:add support for subarch power8 bug#560818 Leno Hou
2015-09-21 14:02 ` Rick "Zero_Chaos" Farina
2015-09-21 17:15   ` Anthony G. Basile [this message]
2015-09-21 18:21     ` Mike Frysinger
2015-09-22  6:34       ` Leno Hou
2015-09-22 13:15         ` Mike Frysinger
2015-09-22 17:00           ` Leno Hou
2015-09-22 20:20             ` Anthony G. Basile
2015-09-22 21:53               ` Mike Frysinger
2015-09-22 22:45                 ` Anthony G. Basile

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=56003B3E.2060001@gentoo.org \
    --to=blueness@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