|
From: | Carol Spears |
Subject: | Re: libtool ignorant of lack of headers in /usr |
Date: | Mon, 17 Oct 2005 12:37:37 -0700 |
User-agent: | Mutt/1.5.9i |
On Mon, Oct 17, 2005 at 08:10:05PM +0200, Ralf Wildenhues wrote: > * 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: > > > > > > 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. :) > native speakers have problems with me even. some ideas are difficult to express no matter what the language. > > > 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? > the spew that had been there, i will repaste it because it might help: undefined reference to `g_intern_static_string' <--this small message told people who are familar with glib that libtool was finding an older version of the library which is located in /usr on my computer. and yes, it would be much more clear (at least to me) if there could be some mention of where the old library had been found. > > 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. > yes, sorry about this. i go on "hearsay" myself when i started this exchange on this bug list. more about what i "heard". i heard that this change in libtool was on purpose and perhaps thought out; although the questions being asked seem to indicated that i was misinformed. > 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 > i had to edit the line some. i am not certain what it is you are looking for so i included my edits incase someone ever tries to report a bug who does not understand this stuff as much as i do. the output should be titled libtool-libpango-1.0.la.txt in the attachments. also my munging of the suggested things to type. i was not able to munge a working objdump for this shared thing. > cat ../pango/libpangoft2-1.0.la > objdump -p ../pango/.libs/libpangoft2-1.0.so > libtool-libpango-1.0.la.txt for this spew. > /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 > am i correct in assuming that you know that "../libtool" will not work? libtool-debug.txt > 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 > interesting. i think the fun was had with ../libtool and it was only so-so in the fun department. libtool-fun.txt i got similar errors when adding -glib and did not paste them. > > 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. > perhaps you could help me explain to the rumor monger i have available to me how this was not intended behavior. this way, i can correct the people who spread the misinformation > > 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. > it was an interesting look into what happens when you type what the gnu guys suggest that you type. i hope that my munging of your suggestions helps to work through the problems. and i apologize for not being able to produce useful output for each request. carol
libtool-libpango-1.0.la.txt
Description: Text document
libtool-libpangoft2-1.0.la.txt
Description: Text document
libtool-debug.txt
Description: Text document
libtool-fun.txt
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |