| 1 |
Dnia 2013-12-29, o godz. 16:40:08 |
| 2 |
Joshua Kinard <kumba@g.o> napisał(a): |
| 3 |
|
| 4 |
> On 12/28/2013 5:58 PM, Michał Górny wrote: |
| 5 |
> > I've noticed today that mips uses the same CHOST value for all three |
| 6 |
> > ABIs it supports: |
| 7 |
> > |
| 8 |
> > arch/mips/mips64/multilib/make.defaults:CHOST_o32="${CHOST}" |
| 9 |
> > arch/mips/mips64/multilib/make.defaults:CHOST_n32=${CHOST} |
| 10 |
> > arch/mips/mips64/multilib/make.defaults:CHOST_n64=${CHOST} |
| 11 |
> > arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_o32="${CHOST}" |
| 12 |
> > arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n32="${CHOST}" |
| 13 |
> > arch/mips/mipsel/mips64el/multilib/make.defaults:CHOST_n64="${CHOST}" |
| 14 |
> > |
| 15 |
> > [...] |
| 16 |
> |
| 17 |
> Matt can probably vouch for this better, but the only two ABIs affected by |
| 18 |
> this are n32 and n64. mips[el]-unknown-linux-gnu implies a 32-bit |
| 19 |
> big/little endian CHOST, which means the o32 ABI. |
| 20 |
> mips64[el]-unknown-linux-gnu means either n32 or n64. So no change should |
| 21 |
> be needed for o32-based installs. |
| 22 |
|
| 23 |
Just to be clear: |
| 24 |
|
| 25 |
profiles/arch/mips/mipsel/mips64el/multilib/make.defaults: |
| 26 |
|
| 27 |
CHOST="mips64el-unknown-linux-gnu" |
| 28 |
|
| 29 |
[...] |
| 30 |
|
| 31 |
CFLAGS_o32="-mabi=32" |
| 32 |
CHOST_o32="${CHOST}" |
| 33 |
|
| 34 |
CFLAGS_n32="-mabi=n32" |
| 35 |
CHOST_n32="${CHOST}" |
| 36 |
|
| 37 |
CFLAGS_n64="-mabi=64" |
| 38 |
CHOST_n64="${CHOST}" |
| 39 |
|
| 40 |
So in this case, o32 actually uses mips64el-unknown-linux-gnu, unless |
| 41 |
I'm missing something. |
| 42 |
|
| 43 |
-- |
| 44 |
Best regards, |
| 45 |
Michał Górny |
Archives