RE: libtool-1.5.4 problem compiling xfsprogs

Here's the configure command I used:
./configure --prefix=/usr \
               --enable-shared=no

As you can see, I didn't specify a compiler name.


Mark Post

-----Original Message-----
From: Bob Friesenhahn [mailto:bfriesen@xxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, April 07, 2004 3:49 PM
To: Post, Mark K
Cc: 'bug-libtool@xxxxxxx'
Subject: Re: libtool-1.5.4 problem compiling xfsprogs


On Wed, 7 Apr 2004, Post, Mark K wrote:

> I upgraded libtool to 1.5.4 yesterday, and then today when I tried to 
> build the newer version of xfsprogs, I get this error: # make
> === include ===
> rm -f attr
> ln -s . attr
> === libmisc ===
> /usr/bin/libtool --mode=compile gcc -g -DDEBUG -funsigned-char -Wall
> -I../include -DVERSION=\"2.4.15\" -DLOCALEDIR=\"/usr/share/locale\"
> -DPACKAGE=\"attr\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64   -D_REENTRANT
> -fno-strict-aliasing -c quote.c
> libtool: compile: unable to infer tagged configuration
> libtool: compile: specify a tag with `--tag'
> make[1]: *** [quote.lo] Error 1
> make: *** [default] Error 2
>
>
> >From what I can tell, libtool should only to try to infer something 
> >when
> --mode= is not specified.  Is that correct?

No.  If the tag is not specified using the --tag= option, then libtool will
guess the tag from the first word after the libtool options.  If you used
'CC=gcc -g' while running configure, then libtool won't be able to guess the
tag correctly since it parses the command line as presented.

Use CC=gcc CFLAGS=-g in order to avoid tag name mismatches.

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