Re: libtool ignorant of lack of headers in /usr

[Ralf Wildenhues]

Hi Carol,

* Carol Spears wrote on Mon, Oct 17, 2005 at 07:30:29PM CEST:
> On Mon, Oct 17, 2005 at 06:30:45PM +0200, Ralf Wildenhues wrote:
> > * Carol Spears wrote on Mon, Oct 17, 2005 at 05:46:48PM CEST:
> > > 
> > > i am using (GNU libtool) 1.5.20 Debian 1.5.20-2 (1.1220.2.287 2005/08/31
> > > 18:54:15) to build glib, pango and gtk+ from cvs.
> > 
> > OK.  Which architecture are you on?
> > 
> address@hidden:~$ uname -a
> Linux treva 2.6.9 #1 Sun Feb 13 11:44:32 PST 2005 i686 GNU/Linux
> 
> whatelse would you like to know?

See below.

> > > /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall   -o pangoft2topgm
> > > pangoft2top
> > > gm.o renderdemo.o argcontext.o ../pango/libpango-1.0.la
> > > ../pango/libpangoft2-1.0
> > > .la -lfontconfig   -lfreetype -lz 
> > > gcc -g -O2 -Wall -o .libs/pangoft2topgm pangoft2topgm.o renderdemo.o
> > > argcontext.o  ../pango/.libs/libpango-1.0.so 
> > > ../pango/.libs/libpangoft2-1.0.so -lfontconfig /usr/lib/libfreetype.so -lz
> > > ../pango/.libs/libpango-1.0.so: undefined reference to 
> > > `g_intern_static_string'
> > > collect2: ld returned 1 exit status
> > > make[2]: *** [pangoft2topgm] Error 1
> > > 
> > > the way i understand it, libtool is finding .la files that were
> > > installed by debian.  this breaks an otherwise sane build system.  this
> > > negates anything that ldconfig does. 
> > 
> > I don't understand you at all.  Might be a language barrier, or
> > something else.
> > 
> yes.  i am a user.  i went from playing star trek and adventure on a
> teletype machine in 1982 to more than a decade of nothing computer at
> all and then a big jump into gnu stuff  in 1998.  i know a lot and know
> nothing at the same time.  language will be a problem.

Oh, I meant *me*.  I am not a native speaker.  :)

> > What do you expect to happen?
> i expect that when the compiler linker knows to use the files from
> /usr/local that libtool will also.

I actually don't think this is the issue you are seeing.
Above link line contains no mention of glib, see?

> > Which package is this that you are building (sorry if the question seems
> > dense to you)?
> not at all.  my goal is to build my desktop (xfce), my graphics app
> (gimp) and my media player 
*snip*

OK.

> i started with glib.  glib is a gnu wrapper around libc.  right now, on
> my computer i have a functional glib installed in /usr/lib and a fully
> enabled newer glib installed in /usr/local/lib.  every single tool in
> the build system understands this with the exception of libtool.

Please, don't infer things.  I have a hard time to distinguish between
facts and conclusions here.

> the broken build is pango, the font renderer.  it seems to break during
> testing which means (i think) that the build is complete.  this does
> nothing to help with my aggravation level.

Hmm.

> > Could you paste the .la files referenced in above link line?
> > 
> i would like libtool to see this file:
> address@hidden:~$ ls -l /usr/local/lib/libglib-2.0.la
> -rwxr-xr-x  1 root root 829 2005-10-16 22:54
> /usr/local/lib/libglib-2.0.la
> 
> instead libtool sees this file:
> address@hidden:~$ ls -l /usr/lib/libglib.la
> -rw-r--r--  1 root root 714 2005-05-04 03:13 /usr/lib/libglib.la

Does it?  Let's see.

OK, here's a list of very precise things to answer, so as to avoid any
misunderstandings.  Please do the following and post all output (stdout
plus stderr!) back here, ordered:  Go to the directory where
`pangoft2topgm' should be created, then execute this (watch out, long
lines!):

cat ../pango/libpango-1.0.la
objdump -p ../pango/.libs/libpango-1.0.so

cat ../pango/libpangoft2-1.0.la
objdump -p ../pango/.libs/libpangoft2-1.0.so

/bin/sh ../libtool --debug --mode=link gcc  -g -O2 -Wall   -o pangoft2topgm 
pangoft2top gm.o renderdemo.o argcontext.o ../pango/libpango-1.0.la 
../pango/libpangoft2-1.0.la -lfontconfig   -lfreetype -lz

Now, just for fun, let's add /usr/local/lib to the link line:
/bin/sh ../libtool --mode=link gcc  -g -O2 -Wall   -o pangoft2topgm pangoft2top 
gm.o renderdemo.o argcontext.o -L/usr/local/lib ../pango/libpango-1.0.la 
../pango/libpangoft2-1.0.la -lfontconfig   -lfreetype -lz

Now, just for fun, let's _also_ add -lglib to the link line:
/bin/sh ../libtool --mode=link gcc  -g -O2 -Wall   -o pangoft2topgm pangoft2top 
gm.o renderdemo.o argcontext.o ../pango/libpango-1.0.la 
../pango/libpangoft2-1.0.la -L/usr/local/lib -lglib -lfontconfig   -lfreetype 
-lz


Note that I need all answers in order to be able to predictably say what
the underlying problem might be, and how a reliable solution will look
like.

> i am sorry, i did not want to appear rude, i wanted to appear as an old
> and semi-seasoned fan of gnu build tools who is confused and
> disheartened because it doesn't work any longer.  i love the gnu build
> tools.  no matter how my current frustration appears here, please
> understand this underlying love.

Oh, never mind, you're doing fine.

> > (another reason may be that whoever provided your CPPFLAGS with the
> > -I/usr/local/include entry should've also provided LDFLAGS with
> > -L/usr/local/lib or similar; but then again, `-lglib' does not even show
> > up in the line beginning with `/bin/sh ../libtool --mode=link', so that
> > seems rather unlikely)
> > 
> i am using a shell script to make my build go easier.  i actually had to
> heavily edit this document:
*snip*

OK.

> maybe i am just in need of a way to tell libtool to look only in
> /usr/local
> 
> the one thing i understand is that i do not understand the reasons my
> build system was successful for so long.  it is causing me problems
> understanding the reason it is suddenly broken as well.

Well, with the answers to above questions it might be possible to deduce
the cause.

Cheers,
Ralf