| 1 |
On 04/28/2014 04:33 PM, Ruud Koolen wrote: |
| 2 |
> On Monday 28 April 2014 10:30:58 Michael Haubenwallner wrote: |
| 3 |
>> IIRC, aixdll is needed by portage itself for these tasks: |
| 4 |
>> *) extract the binary dependencies for preserve-libs feature |
| 5 |
>> *) merge library archives containing shared objects - even with |
| 6 |
>> "aix-soname". |
| 7 |
> |
| 8 |
> Then I think it needs to be installed before gcc which builds aix-soname |
| 9 |
> libraries, but not necessarily any earlier than that. |
| 10 |
|
| 11 |
It should be fine to have it installed somewhere before the final 'emerge -e' |
| 12 |
actually, as this will recreate the NEEDED.XCOFF file anyway. |
| 13 |
|
| 14 |
<snip> |
| 15 |
|
| 16 |
>>> If I understand correctly, dev-libs/libiconv is a dependency for a lot of |
| 17 |
>>> programs, including gcc, and as such needs to be installed before gcc. |
| 18 |
>>> This is clear. Are there any other packages in the early bootstrap that |
| 19 |
>>> depend on it? Could it be installed immediately before gcc? I see that it |
| 20 |
>>> was recently moved from immediately before gcc, to one of the first |
| 21 |
>>> things in stage3. Why is this? What hell are you avoiding this way that I |
| 22 |
>>> should retain? |
| 23 |
>> |
| 24 |
>> Okay, you've asked: The "hell with shared libiconv.a" is this one: |
| 25 |
>> |
| 26 |
>> [snip] |
| 27 |
> |
| 28 |
> Hellish indeed. |
| 29 |
> |
| 30 |
> libiconv used to be built immediately before gcc, but recently you moved it to |
| 31 |
> very early stage3. Why is that? As far as I can see, gcc is the earliest |
| 32 |
> stage3 package that uses iconv. Or is there a hidden dependency somewhere? |
| 33 |
> Evidently you changed it in response to a bug, but I don't see it. |
| 34 |
|
| 35 |
Looking again now I remember it has been app-shells/bash I need libiconv for. |
| 36 |
Otherways, as soon as libiconv is emerged, the bash binary is broken. |
| 37 |
|
| 38 |
/haubi/ |
Archives