1 |
Robin H. Johnson schrieb: |
2 |
> On Sun, Oct 18, 2009 at 10:26:37PM -0400, Mike Frysinger wrote: |
3 |
>> On Sunday 18 October 2009 14:49:09 Thomas Sachau wrote: |
4 |
>>> Robin H. Johnson schrieb: |
5 |
>>>> On Mon, Oct 12, 2009 at 04:50:23PM -0400, Mike Frysinger wrote: |
6 |
>>>>> what exactly does this "lib32" do ? naming USE flags according to |
7 |
>>>>> specific ABI implementations is a bad idea. you have to forget special |
8 |
>>>>> casing anything to "lib32 vs lib64". amd64, while the most common, is |
9 |
>>>>> hardly extensible. we must handle multiple ABIs which easily might have |
10 |
>>>>> the same bitsize. |
11 |
>>>> The canonical example for this does still remain MIPS I believe. |
12 |
>>>> |
13 |
>>>> The most common ABIs in MIPS are: |
14 |
>>>> o32, n32 - Both in Gentoo releases |
15 |
>>>> n64 - Was experimentally done in Gentoo |
16 |
>>>> (default-linux/mips/2007.1-dev/generic-be/n64) o64, eabi, meabi, nubi - |
17 |
>>>> Not sure if they were were ever released in any way. |
18 |
>>>> |
19 |
>>>> Crossdev DOES support the full swath of these last I checked it. |
20 |
>>> There is a difference between creating a toolchain and supporting all |
21 |
>>> packages for that arch and every possible ABI you can crosscompile. |
22 |
>>> |
23 |
>>> Currently i only support amd64 since thats the only ARCH i know and have |
24 |
>>> access to. If i get enough details to implement other ARCHes and some way |
25 |
>>> to test it there, i might try it for those other ARCHes too. |
26 |
>> we're not asking you to implement support for these ABIs, just to keep in mind |
27 |
>> that any implementation that does not scale and/or hardcodes to a single set |
28 |
>> of ABIs isnt a proper solution |
29 |
> My main objection thusfar is hardcoding the names as lib64/lib32. |
30 |
> |
31 |
> Is there any specific reason you're using the content of the |
32 |
> LIBDIR_${ABI} variable? Maybe using the $ABI string as the USE flag |
33 |
> would be better, in some form of USE_EXPAND manner (cannot use them raw |
34 |
> as I believe we still have some code in the form of 'use $ARCH', which |
35 |
> might not behave sanely if say both amd64 and x86 were set. |
36 |
> |
37 |
> Egs: |
38 |
> multilib AMD64: |
39 |
> USE="abi_x86 abi_amd64" |
40 |
> |
41 |
> Multilib PPC64: |
42 |
> USE="abi_ppc abi_ppc64" |
43 |
> |
44 |
> Multilib MIPS (SGI hardware) |
45 |
> USE="abi_n32 abi_n64" |
46 |
> |
47 |
> Possible valid multilib sets on MIPS are: |
48 |
> [n32,n64] - at least one Gentoo system like this has been built. |
49 |
> [o32,o64] |
50 |
> [eabi,meabi] - docs fuzzy |
51 |
> [nubi] |
52 |
> |
53 |
|
54 |
I dont mind using some other string here. So those USE flags would be fine for me. They could be |
55 |
USE_EXPANDed to e.g. for multilib amd64 ABI="x86 amd64" |
56 |
|
57 |
Any other comment or suggestions on this part? |
58 |
|
59 |
-- |
60 |
Thomas Sachau |
61 |
|
62 |
Gentoo Linux Developer |