- From: Timothee Besset <ttimo@idsoftware.com>
- Date: Mon, 30 Dec 2002 16:10:47 +0100
- To: www-lib@w3.org
Well actually, the bad things are happening because of ar / multiple .a files and how the GNU linker works. There are cyclic references cropping up everywhere, it's pretty nasty. I have solved the problem now though, after a regular build I do an ar x on all the .a and collapse the object files back into a single .a file. That way I don't get any unresolved anymore. TTimo On Mon, 30 Dec 2002 14:32:18 +0100 Richard Atterer <libwww@list02.atterer.net> wrote: > > On Mon, Dec 30, 2002 at 12:08:56AM +0100, Timothee Besset wrote: > > Does anyone have successful experience statically linking against libwww > > on Linux? Any particular pitfalls to avoid? I have everything working > > fine with dynamic linking, but static linking is giving me a hard time. > > Well, what errors do you get? And what command do you use for linking? > > Are the static libs present in the directory output by > "libwww-config --libs"? > > For example, on my machine it prints out "-L/usr/lib -lwwwzip -lwwwinit > ..." and /usr/lib/libwwwzip.a etc. is present. > > Cheers, > > Richard > > -- > __ _ > |_) /| Richard Atterer | CS student at the Technische | GnuPG key: > | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 > ¯ '` ¯ > >
Received on Monday, 30 December 2002 10:11:40 UTC