System-wide libtool causes ncurses & cdk to mix different versions of CC

[Michał Górny]

Hello,

I'm heavily relying on distcc in my Gentoo boxes, and therefore I'm
building software with CC and CXX specifying exact gcc version.
Therefore, my CC looks like:

  CC=x86_64-pc-linux-gnu-gcc-4.8.3

This also implies that whenever I switch to a newer gcc version, I need
to update CC as well. This usually works but I've just noticed that it
causes ncurses & cdk to occasionally fail to build.

The build error looks like:

  libtool --tag=CC  --mode=link x86_64-pc-linux-gnu-gcc-4.8.3 [...]
  /usr/bin/libtool: line 8979: x86_64-pc-linux-gnu-gcc-4.8.2: command
  not found

which proves that while I've specifically told cdk to use gcc-4.8.3,
libtool tries to use no-longer-installed gcc-4.8.2. I've reported this
issue to our bugzilla as a bug in libtool [1]. However, I was told that
packages aren't supposed to use system-wide libtool but rather generate
a local copy of it that has proper CC substituted.

Subsequently, I've investigated the code used in cdk and came to
conclusions that I've written down in another bug, against cdk this
time [2]. In short, the specific design of cdk and macros used in it
make it very hard and inconvenient to force local libtool on our side.

Therefore, would you be willing to fix the issue on ncurses/cdk side?
I'm not sure if it could be fixed in any way except for using standard
LT_INIT macros and bundling 'ltmain.sh' and other necessities along
with ncurses/cdk.

[1]:https://bugs.gentoo.org/show_bug.cgi?id=515054
[2]:https://bugs.gentoo.org/show_bug.cgi?id=515242
[3]:http://lists.gnu.org/archive/html/bug-ncurses/2004-01/msg00036.html

-- 
Best regards,
Michał Górny

signature.asc
Description: PGP signature