1 |
On 01/17/2014 07:44 PM, Markos Chandras wrote: |
2 |
> On 01/17/2014 06:51 PM, Michał Górny wrote: |
3 |
>> Dnia 2014-01-17, o godz. 18:20:30 |
4 |
>> Markos Chandras <hwoarang@g.o> napisał(a): |
5 |
>> |
6 |
>>> On 01/17/2014 04:47 AM, Michał Górny wrote: |
7 |
>>>> Dnia 2014-01-16, o godz. 17:29:43 "Anthony G. Basile" |
8 |
>>>> <blueness@g.o> napisał(a): |
9 |
>>>> |
10 |
>>>>> On 01/16/2014 04:24 PM, Michał Górny wrote: |
11 |
>>>>>> Because AC_PATH_TOOL uses CHOST and some random Gentoo |
12 |
>>>>>> invention. |
13 |
>>>>> |
14 |
>>>>> I got that AC_PATH_TOOL and AC_CHECK_TOOL prefix whatever utility |
15 |
>>>>> they search for with the canonicalized chost (usually from |
16 |
>>>>> config.guess), but I still don't see why we need this to avoid |
17 |
>>>>> hackery? Can you give me a practial example because right now I |
18 |
>>>>> just don't see a serious problem. |
19 |
>>>> |
20 |
>>>> libgpg-error installs ${CHOST}-gpg-error-config. |
21 |
>>>> |
22 |
>>>> Now libgcrypt (and possibly other tools) are using AC_PATH_TOOL to |
23 |
>>>> find it. If we have proper CHOSTs, they find the right |
24 |
>>>> gpg-error-config and we don't have to put any more effort into |
25 |
>>>> that. Then libgcrypt installs ${CHOST}-libgcrypt-config. |
26 |
>>>> |
27 |
>>>> Now other tools are using AC_PATH_TOOL to find proper |
28 |
>>>> libgcrypt-config. If we have proper CHOSTs, it just works and we |
29 |
>>>> don't have to put any more effort into that. |
30 |
>>>> |
31 |
>>>> Same goes for LLVM & Mesa. |
32 |
>>>> |
33 |
>>>> If we play by the rules nicely, all pieces fit together nicely and |
34 |
>>>> we don't have to worry. If we don't, we ask the developers to spit |
35 |
>>>> Gentoo- specific hackery all over the place. |
36 |
>>>> |
37 |
>>> You need to consider that besides changing CHOST to new stages (which |
38 |
>>> is a lengthy and tiring process), you somehow need to migrate existing |
39 |
>>> users to the new CHOST (no?) otherwise the multilib eclass (or any |
40 |
>>> other eclass/package) that depends on CHOST will be broken as soon as |
41 |
>>> they update their tree and try to install package updates. |
42 |
>>> This is definitely not a pleasant user experience. |
43 |
>> |
44 |
>> Well, I'd like someone who knows better than I do to explain how much |
45 |
>> does changing non-native CHOST affect. I will try to test it a bit by |
46 |
>> changing CHOST_x86=i686-pc-linux-gnu to i386-* locally but an expert |
47 |
>> opinion would be preferred. |
48 |
>> |
49 |
> My comment was not on what side-effects changing the CHOST may have, but |
50 |
> it requires time and effort for every MIPS user out there. You also need |
51 |
> to consider that many people have relatively slow MIPS hardware (routers |
52 |
> and stuff) that will take a good couple of days (if not more) to switch |
53 |
> to a new CHOST. But still, not everyone is going to do it and forcing |
54 |
> them is definitely unpleasant. |
55 |
> |
56 |
|
57 |
fwiw i talked to Michal on IRC and promised to do some tests on my |
58 |
mips64/multilib/n32 box to see what the actual problem is and if his |
59 |
proposal breaks existing installations. Once I have some results, I will |
60 |
reply to the list. |
61 |
|
62 |
-- |
63 |
Regards, |
64 |
Markos Chandras |