[solved] problems with autotools, autoreconf, libtoolize

Message

wazow · Post by **wazow** » Thu Mar 15, 2007 8:32 pm

I am compiling a project from source (not in portage) on a gentoo machine. I face the following problem:

...
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.22, ltmain.sh = 1.5.20) ***

Please run:
  
  libtoolize --copy --force

...

The same project compiles smoothly on my gentoo notebook, so it seems that something got broken on that machine. Running the hint about libtoolize does not help (it reports an error that configure.ac is missing). Can anybody hint what should I fix?

PaulBredbury · Post by **PaulBredbury** » Thu Mar 15, 2007 11:11 pm

Check out the autotools eclass, and its eautoreconf command. Examples:

Code: Select all

find /usr/portage/ -name \*.ebuild | xargs grep -H eautoreconf

wazow · Post by **wazow** » Fri Mar 16, 2007 1:53 pm

PaulBredbury wrote:Check out the autotools eclass, and its eautoreconf command. Examples:
Code: Select all
find /usr/portage/ -name \*.ebuild | xargs grep -H eautoreconf

Can you be slightly more specific? I am not a gentoo developr, so I do not even know what eclass is. Note that this thing I am compiling is not an ebuild even. I have tried to run the command that you suggested, but it seems just to report lots of ebuild that do eautoreconf, and I do not even know what eautoreconf is.

wazow · Post by **wazow** » Fri Mar 16, 2007 2:10 pm

wazow wrote:Can you be slightly more specific? I am not a gentoo developr, so I do not even know what eclass is. Note that this thing I am compiling is not an ebuild even. I have tried to run the command that you suggested, but it seems just to report lots of ebuild that do eautoreconf, and I do not even know what eautoreconf is.

I have sorted it out myself: I have found out that eautoreconf is a portage function that calls autoreconf. I do not really know what autoreconf does, but I just wen to the main dir of the source tree and run it. Then I still had to run libtoolize --copy --force, as the script has suggested. And then everything builds automagically as per build instructions of that package.