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: Tue, 22 Sep 2015 16:20:54 -0400 [thread overview]
Message-ID: <5601B826.6000609@gentoo.org> (raw)
In-Reply-To: <CAGQVrL8Sc_8K+GkRA8F8yFdEehW4oDFPH+5ZEjP0qfVrSDKaBw@mail.gmail.com>
On 9/22/15 1:00 PM, Leno Hou wrote:
> On Tue, Sep 22, 2015 at 9:15 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>
>> On 22 Sep 2015 14:34, Leno Hou wrote:
>>> On Tue, Sep 22, 2015 at 2:21 AM, Mike Frysinger <vapier@gentoo.org>
>> wrote:
>>>> On 21 Sep 2015 13:15, Anthony G. Basile wrote:
>>>>> On 9/21/15 10:02 AM, Rick "Zero_Chaos" Farina wrote:
>>>>>> On 09/21/2015 08:38 AM, Leno Hou wrote:
>>>>>>> + self.settings["CHOST"]="powerpc64le-linux-gnu"
>>>>> 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.
>>>> powerpc64le-linux-gnu is a valid tuple (vendor can generally be
>> omitted),
>>>> but in Gentoo we do use "unknown" for our ppc ports. so do as Anthony
>>>> says ;).
>>>> -mike
>>>>
>>> When set CHOST="powerpc64le-linux-gnu", successfully compiled stage1.
>>> But CHOST="powerpc64-unknown-linux-gnu", something happens as following.
>>> https://bpaste.net/show/189b2b12d8e2
>>>
>>> So I think CHOST="powerpc64le-linux-gnu" would be better.
>> i think you're misreading things. we didn't say
>> "powerpc64-unknown-linux-gnu",
>> we said "powerpc64le-unknown-linux-gnu".
>> -mike
>>
> I've tested CHOST="powerpc64le-unknown-linux-gnu" and proved you're right.
> The results is that got compiler called "powerpc64le-unknown-linux-gnu-*"
> in stage 1.
> So could you help me to commit PATCH v2 ? thanks.
> -Leno Hou
>
Where is it? I have commit to the catalyst repo.
--
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
next prev parent reply other threads:[~2015-09-22 20:21 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
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 [this message]
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=5601B826.6000609@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