When trying to emerge libtool, as part of the "prefix Gentoo" bootstrapping sequence for x86 Solaris 10, I get this error (/opt/g2 is my EPREFIX): /opt/g2/usr/portage/sys-devel/libtool/libtool-1.5.23b.ebuild: line 88: lt_setup: command not found I tried to look around for a definition of lt_setup, but could not find it; there is nothing under /opt/g2/usr/portage/eclass for example. Later on the ebuild fails with these messages, possibly a consequence of lt_setup not having been done: checking for correct ltmain.sh version... no configure: error: *** [Gentoo] sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.23b, ltmain.sh = ) *** Please run: 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: !!! /opt/g2/var/tmp/portage/sys-devel/libtool-1.5.23b/work/libtool-1.5.23b/config.log !!! ERROR: sys-devel/libtool-1.5.23b failed. Call stack: ebuild.sh, line 1561: Called dyn_compile ebuild.sh, line 913: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile libtool-1.5.23b.ebuild, line 89: Called econf ebuild.sh, line 516: 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 '/opt/g2/var/tmp/portage/sys-devel/libtool-1.5.23b/temp/build.log'.
Created attachment 121832 [details] The logfile referred to in the console printout
I retried by specifying that =sys-devel/libtool-1.5.22 should be merged instead. This version of the ebuild does not have the lt_setup problem (it is defined within the ebuild itself). However, the emerge operation still fails, now with configure: error: *** [Gentoo] sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.22, ltmain.sh = ) *** Please run: libtoolize --copy --force if appropriate, please contact the maintainer of this package (or your distribution) for help.
Good news, I have found the reason why libtool-1.5.22 did not emerge properly for me. It turned out that I was using Solaris egrep, which does not extract the VERSION info as intended from the 'configure' file of the unpacked tarball, thus causing the "sanity check" failure. In conclusion then, I leave this bug as "NEW". It pertains specifically to the libtool-1.5.23b ebuild, and it should be noted that the "sanity check" failure is unrelated to the actual issue: there is no definition of lt_setup.
so why did it find Solaris' egrep? Does it look for egrep before grep -E or something? It looks to me like egrep also gets installed by the grep installation in the tmp dir.
(In reply to comment #4) > so why did it find Solaris' egrep? Does it look for egrep before grep -E or > something? It looks to me like egrep also gets installed by the grep > installation in the tmp dir. > grobian, looks like this bug can be closed. You are correct that egrep gets installed via bootstrap. Libtool 1.5.24 installed just fine for me on the same platform. I would suspect that the OP didn't bootstrap grep or had a wierd PATH. Just a guess though.
Resolving as INVALID only because the libtool version referenced in this bug is no longer in the prefix tree. Thanks for reporting..
