| 1 |
Hi, |
| 2 |
|
| 3 |
The vast majority of libtool-based programs use configure script to |
| 4 |
generate libtool. However, a few non-autoconf packages also use libtool |
| 5 |
by calling system-installed /usr/bin/libtool. The problem is that this |
| 6 |
libtool hardcodes the values of CC/CXX at its' build time, so unless it |
| 7 |
is rebuilt frequently, packages end up using the stale values. |
| 8 |
The problem is known since 2005 [1] and hasn't been resolved yet. |
| 9 |
|
| 10 |
I can think of two ways of solving it: |
| 11 |
|
| 12 |
1. We could patch system-installed libtool to respect environment |
| 13 |
variables such as CC, CXX, etc. This will probably require carrying |
| 14 |
a (possibly non-trivial) patch forever. On the bright side, libtool is |
| 15 |
not exactly a package seeing frequent releases. I mean, the current |
| 16 |
version is from 2015. |
| 17 |
|
| 18 |
2. We could regenerate libtool and force local instance of libtool |
| 19 |
in the packages needing it. The main advantage of this is that it's |
| 20 |
a no-brainer. I could make a quick eclass that does configure a local |
| 21 |
instance and prepends it into PATH. |
| 22 |
|
| 23 |
WDYT? |
| 24 |
|
| 25 |
|
| 26 |
[1] https://bugs.gentoo.org/88596 |
| 27 |
|
| 28 |
-- |
| 29 |
Best regards, |
| 30 |
Michał Górny |
Archives