Re: cvs build prob

[Bob Friesenhahn]

I saw a problem similar to this but resolved it by moving the 
installed libtool.m4 to the side, running aclocal, and re-running the 
libtool bootstrap script.

After that I hit the VPATH problems mentioned earlier on the 
libtool-patches list and am dead in the water. :-)

Bob

On Mon, 26 Jul 2004, Patrick Welche wrote:

> I get:
>
> libtool: Version mismatch error.  This is libtool 1.5b, revision AR=ar
> AR_FLAGS...
> libtool: but the definition used by this AC_PROG_LIBTOOL comes from revision
> libtool: 1.1527.
> libtool: You should recreate aclocal.m4 with macros from revision AR=ar
> AR_FLAGS...
> libtool: of libtool 1.5b and run autoconf again.
>
> when trying to make cvs-libtool.
>
> Strangely, this looks right:
>
> macro_revision=1.1527
> macro_version=1.5b
>
> My reason for suspecting sed, is that I don't use GNU sed, and when running
> configure in cvs-libtool, I see:
>
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
> sed: 1: ""s/\*/\\\*/g"": invalid command code "
> checking for g++ option to produce PIC... -fPIC -DPIC
>
> which looks like line 3404 of libtool.m4. Thing is, that line hasn't changed
> in a while, and I'm sure I didn't see the above error since..
>
> Checking ksh now..
>
> Cheers,
>
> Patrick
>
>
> _______________________________________________
> Libtool mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/libtool

======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen