#215 Celestia-svn4593 build fails with libtool-2.2.6 error

v1.6
open
nobody
5
2009-01-11
2009-01-11
No

I tried to build Celestia rev 4593.
First, I ran autoreconf -ivf
Configure ran without problems (--prefix/usr --disable-nls --with-gtk).
Make exits with the following error:

<snip>
../../libtool: line 451: CDPATH: command not found
../../libtool: line 1129: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
libtool: and run autoconf again.
make[4]: *** [celestia] Error 63
make[4]: Leaving directory `/usr/pkgmk/build/celestia/src/celestia-1.6.0/src/celestia'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/pkgmk/build/celestia/src/celestia-1.6.0/src/celestia'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/pkgmk/build/celestia/src/celestia-1.6.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/pkgmk/build/celestia/src/celestia-1.6.0'
make: *** [all] Error 2

Software used:
gcc-4.3.2
m4-1.4.12
libtool-2.2.6
autoconf-2.63

Discussion

  • Predrag Ivanovic

    I found a fix/workaround of sorts.
    I deleted all lines below "-# libtool.m4 - Configure libtool for the host system. -*-Autoconf-*-"
    from acinclude.m4, ran autoreconf -ivf, configure, make and celestia builds without problems.
    It works fine-ish after that, but about that in another bug.

     
  • Predrag Ivanovic

    I found a fix/workaround of sorts.
    I deleted all lines below "-# libtool.m4 - Configure libtool for the host system. -*-Autoconf-*-"
    from acinclude.m4, ran autoreconf -ivf, configure, make and celestia builds without problems.
    It works fine-ish after that, but about that in another bug.

     
  • Pat Suwalski

    Pat Suwalski - 2009-02-11

    The solution is to not run autoreconf with -ivf. Safest is:

    aclocal;autoheader;autoconf;automake

    But

    autoreconf

    works as well. This has to do with how the KDE "admin" directory works. Libtoolize will always try to overwrite with newer files, but they're not compatible.

     
  • Chris Laurel

    Chris Laurel - 2009-02-14

    So it sounds like we can mark this 'not a bug' and close it?

     

Log in to post a comment.