Unable to install mod_php because lcms-1.13 fails
*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.16, ltmain.sh = 1.5) ***
Please run:
libtoolize --copy --force
if appropriate, please contact the maintainer of this
package (or your distribution) for help.
!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/lcms-1.13/work/lcms-1.13/config.log
I've already tried this, ie. going directly to /var/tmp/portage/lcms-1.13/work/lcms-1.13/ and running the libtoolize command above. After doing so, I tried the usual suspects (./configure, followed by make and make install), no errors appearing. After that, I tried emerging mod_php (or just php, for that matter), and it still tries to emerge lcms-1.13 among the packages (I'm always using the -av options to get a full overview of what's being installed).
Now what? Any ideas?
5 Replies
>>> Unpacking source...
>>> Unpacking lcms-1.13.tar.gz to /var/tmp/portage/lcms-1.13/work
* Using GNU config files from /usr/share/libtool
* Updating config.sub [ ok ]
* Updating config.guess [ ok ]
* Patching ${S}/ltmain.sh ...
* Applying portage-1.4.1.patch ...
* Applying max_cmd_len-1.5.0.patch ...
* Applying sed-1.4.3.patch ...
* Applying tmp-1.3.5.patch ...
* Applying uClibc/libtool patches ...
* Running autoreconf...
* Running libtoolize...
* Patching ${S}/ltmain.sh ...
* Portage patch seems to be already applied.
* Please verify that it is not needed.
* Applying sed-1.3.4.patch ...
* Applying uClibc/libtool patches ...
>>> Source unpacked.
-Brian
@absolutefunk:
emerge –oneshot libtools fixed it for me (or at the least the part that hung me up before).
-Brian
Didn't seem to help much (no change). Do I need to unmerge libtool first?
It's successfully compiling now. No errors so far. Odd indeed.
First step: visit http://bugs.gentoo.org
Second step: do a search. I used: ALL lcms libtool
It returned a list of three bugs. This looks to be your bug for lcms 1.13 and libtool:
http://bugs.gentoo.org/show_bug.cgi?id=74442
It's fixed in 1.13-r1… or you can apply a patch for 1.13 and rebuild the digest (easy). I see you've found a different workaround.