Re: xfs-progs and libtool-1.5.2 issues

[Kostadin Karaivanov <larry@xxxxxxxxxxx>]

Nathan Scott wrote:
> On Thu, Feb 19, 2004 at 06:18:17PM +0200, Kostadin Karaivanov wrote:
>
> > Recently I upgarded my libtool to 1.5.2 (slackware-current)
> > nad I'm n unable to compile xfs-cms anymore
> > following error is excerpt from
> > make in xfs-cmds/attr
> >
> > make -C . default
> > make[1]: Entering directory `/usr/src/xfs-cmds/attr'
> > === 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[2]: *** [quote.lo] Error 1
> > make[1]: *** [default] Error 2
> > make[1]: Leaving directory `/usr/src/xfs-cmds/attr'
> > make: *** [default] Error 2
>
>
> I have libtool 1.5.2 (Debian unstable), and it works fine here.
> The libtool script is a bit of a rats nest, but from a quick
> read it looks like you may have CC set to something other than
> what libtool thinks the base compiler is..?  You may be able
It apears so....
> to find out more by running "sh -x libtool ..." from within the
> Makefiles and then seeing where it gets confused.  If you have
> a working libtool script, might be easier to diff it with your
> current version...  (I've attached my /usr/bin/libtool - is it
> any different to yours?)
>
> cheers.
After little diffing I found that the only noticeble difference
between your libtool and mine is in the lines defining LTCC and CC.
In Slackwares libtool they are defined as
LTCC="i486-slackware-linux-gcc"
CC="i486-slackware-linux-gcc"
which in turn is hyperlink to gcc-3.3.3
both are present.....
when I changed those definitions to simple "gcc" (which also is 
hyperlink to gcc-3.3.3) everything i OK again