I was doing a simple straight-forward addition of xorg-x11 and...
fonconfig died with a message about the libtool in .m4 and .sh mismatch.
It said to libtoolize --copy --force, and I figured out on my own WHERE to do that. :-)
Continuing with emerge --resume --skipfirst xorg-x11 seems to be going okay, as it is madly compiling away a zillion things as usual.
Haven't finished it or anything, mind you...
Steps to Reproduce:
1. emerge --sync as of JULY 19 2007
2. Yes, I did emerge portage as instructed
3. emerge xorg-x11
POSSIBLE RED HERRINGS:
I was dinking around with autoconf / automake / libtool (and flex and bison) to install PHP from CVS according to these instructions:
I HAD rolled back my autoconf / automake /libtool as instructed, but missed the flex version requirement (which has just been changed on that page to be idiot-proof, thanks to me being an idiot).
I believe I am current in my make tools:
In addition to /usr/bin/libtool (1.5.23b) I have a /usr/local/bin/libtool which I downloaded and compiled from source which is version 1.4.3 as I thought PHP needed that. It doesn't, and I should probably nuke it.
checking for correct ltmain.sh version... no
*** [Gentoo] sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.23b, ltmain.sh = 1.4.3) ***
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! ERROR: media-libs/fontconfig-2.4.2 failed.
ebuild.sh, line 1621: Called dyn_compile
ebuild.sh, line 973: Called qa_call 'src_compile'
ebuild.sh, line 44: Called src_compile
fontconfig-2.4.2.ebuild, line 41: Called econf '--disable-docs' '--disable-docbook' '--localstatedir=/var' '--with-docdir=/usr/share/doc/fontconfig-2.4.2' '--with-default-fonts=/usr/share/fonts' '--with-add-fonts=/usr/local/share/fonts,/usr/X11R6/lib/X11/fonts' '--disable-libxml2'
ebuild.sh, line 578: Called die
!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/media-libs/fontconfig-2.4.2/temp/build.log'.
The complete log is available here:
I would have expected it to use the same libtool I'd get from the command line environment, and not find the one in /usr/local/bin/libtool as it seems to have done?...
Or is that a red herring and this is broken for everybody?...
Even if it's just my old version of libtool off in the /usr/local/bin directory, that shouldn't have interfered, imho, as a naive user...
I'll try again after I nuke that just to see what happens.
Mainly because I'm unsure of stability if some other software didn't catch the mis-match and used the wrong libtool... Got no idea what that would do.
I'm leaving severity at Normal, as I don't know enough to choose correctly.
(In reply to comment #0)
> In addition to /usr/bin/libtool (1.5.23b) I have a /usr/local/bin/libtool which
> I downloaded and compiled from source which is version 1.4.3 as I thought PHP
> needed that. It doesn't, and I should probably nuke it.
Well, that's clearly your problem, remove it. :)
(In reply to comment #1)
> (In reply to comment #0)
> > In addition to /usr/bin/libtool (1.5.23b) I have a /usr/local/bin/libtool which
> > I downloaded and compiled from source which is version 1.4.3 as I thought PHP
> > needed that. It doesn't, and I should probably nuke it.
> Well, that's clearly your problem, remove it. :)
Well, yeah, but what if a developer needs other versions of libtool laying around?...
More importantly, why is emerge using the one from /usr/local/lib sometimes but not other times?
Erm, you certainly don't need libtool-1.4.3 for anything. If you insist on having it installed, move it out of your $PATH (/usr/local/bin) before you emerge anything; local cruft in /usr/local is not our problem.
(In reply to comment #3)
> Erm, you certainly don't need libtool-1.4.3 for anything. If you insist on
> having it installed, move it out of your $PATH (/usr/local/bin) before you
> emerge anything; local cruft in /usr/local is not our problem.
Forgive me for not being clear enough.
/usr/local/bin is not in root's path.
%root> `libtool --version` outputs 1.5.23b as expected.
emerge then goes and uses the libtool NOT in my path, at some point in the process, afaict...
If I was dumb enough to have the old version in my path when I started emerge, I wouldn't have posted it as a bug in the first place.
I'm stupid, but not THAT stupid. :-)
Perhaps it does some kind of 'su' to a different user where /usr/local/bin is in the path?
My assumption was that everything was done as 'root' as only root can emerge (at least without tweaking more than I have)
emerge --info -v | grep $PATH