| 1 |
On 22 Sep 2015 14:34, Leno Hou wrote: |
| 2 |
> On Tue, Sep 22, 2015 at 2:21 AM, Mike Frysinger <vapier@g.o> wrote: |
| 3 |
> |
| 4 |
> > On 21 Sep 2015 13:15, Anthony G. Basile wrote: |
| 5 |
> > > On 9/21/15 10:02 AM, Rick "Zero_Chaos" Farina wrote: |
| 6 |
> > > > On 09/21/2015 08:38 AM, Leno Hou wrote: |
| 7 |
> > > >> + self.settings["CHOST"]="powerpc64le-linux-gnu" |
| 8 |
> > > |
| 9 |
> > > The CHOST is incorrect. It should powerpc64le-unknown-linux-gnu. Leno, |
| 10 |
> > > can you please try to switch it to that and do another catalyst run. |
| 11 |
> > > You can begin with your current stage3 with the above CHOST and it |
| 12 |
> > > should work out correctly to the new CHOST name. In another place you |
| 13 |
> > > said there is no compiler "powerpc64le-unknown-linux-gnu" but that makes |
| 14 |
> > > no sense. The tuple is parsed by gnuconfig script and it should work |
| 15 |
> > > like all other CHOST names we have in gentoo. |
| 16 |
> > |
| 17 |
> > powerpc64le-linux-gnu is a valid tuple (vendor can generally be omitted), |
| 18 |
> > but in Gentoo we do use "unknown" for our ppc ports. so do as Anthony |
| 19 |
> > says ;). |
| 20 |
> > -mike |
| 21 |
> > |
| 22 |
> |
| 23 |
> When set CHOST="powerpc64le-linux-gnu", successfully compiled stage1. |
| 24 |
> But CHOST="powerpc64-unknown-linux-gnu", something happens as following. |
| 25 |
> https://bpaste.net/show/189b2b12d8e2 |
| 26 |
> |
| 27 |
> So I think CHOST="powerpc64le-linux-gnu" would be better. |
| 28 |
|
| 29 |
i think you're misreading things. we didn't say "powerpc64-unknown-linux-gnu", |
| 30 |
we said "powerpc64le-unknown-linux-gnu". |
| 31 |
-mike |
Archives