| 1 |
On Mon, 11 Jan 2021 18:36:31 +0000 Peter Stuge wrote: |
| 2 |
|
| 3 |
>Jaco Kroon wrote: |
| 4 |
>> > I can think of two ways of solving it: |
| 5 |
>> > |
| 6 |
>> > 1. We could patch system-installed libtool to respect environment |
| 7 |
>> > |
| 8 |
>> > 2. We could regenerate libtool and force local instance of libtool |
| 9 |
>> > in the packages needing it. |
| 10 |
>> |
| 11 |
>> 3. Have it always use some fixed compiler somewhere (ie, compile it |
| 12 |
>> |
| 13 |
> |
| 14 |
>4. Make gcc-config regenerate libtool, otherwise as 2. |
| 15 |
> |
| 16 |
> |
| 17 |
>//Peter |
| 18 |
> |
| 19 |
|
| 20 |
5.) Try to replace GNU libtool with sys-devel/slibtool |
| 21 |
|
| 22 |
slibtool is aimed to be a drop-in replacement although at the current |
| 23 |
state it still has a couple of hiccups. I've created a tracker bug at |
| 24 |
[1] to track all issues arising from using slibtool instead of GNU |
| 25 |
libtool. |
| 26 |
|
| 27 |
Cheers |
| 28 |
Lars |
| 29 |
|
| 30 |
[1] https://bugs.gentoo.org/765709 |
| 31 |
-- |
| 32 |
Lars Wendler |
| 33 |
Gentoo package maintainer |
| 34 |
GPG: 21CC CF02 4586 0A07 ED93 9F68 498F E765 960E 9B39 |
Archives