[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [xml] Generating a correct xml2-config for use with --libs
- From: Daniel Veillard <veillard redhat com>
- To: Gary Pennington <Gary Pennington sun com>
- Cc: Stefan Kost <kost imn htwk-leipzig de>, xml gnome org
- Subject: Re: [xml] Generating a correct xml2-config for use with --libs
- Date: Thu, 13 Jun 2002 11:26:19 -0400
On Thu, Jun 13, 2002 at 04:10:58PM +0100, Gary Pennington wrote:
> Daniel Veillard wrote:
> > xmlNewDoc can dereference the socket code. Moreover not all system
> >have shared library, some don't even have dynamic ones.
> >
> This statement is completely opaque to me. If you are saying that it is
> possible that you may invoke a function in libxml2 that then invokes a
> function in libsocket, fine. That's the job of the linker.
You seems to only consider late linking i.e. run-time one, and I'm
trying to explain that some systems need compile time linking informations
to be able to simply compile and link the program.
> With respect to older platforms which don't have shared objects, how
> about --static-libs. That would be a good solution and would allow the
> more modern platforms to keep things clean whilst still catering for
> legacy platforms.
Some systems have shared libraries, but can record dependancies to a
shared library only in a program instance, not in shared libraries. Not
everything is ELF or similarily capable. If you know your platform can do
it, fine, as I said provide a conditional patch, but you can't assume this
to be the case on all platforms. Just look at the bug which just landed
in the bugzilla during this exchange:
http://bugzilla.gnome.org/show_bug.cgi?id=85161
all platforms have serious divergences on the way they handle shared
libraries, and what looks a simple optimization on platform A can simply
break linking on a whole set of other platforms, hence my request to make
this system specific.
> I appreciate that. However, as I said, when libxml2 is built it is
> linked with the necessary libraries (socket, etc) and there is no need
> for the application itself to also express this dependancy. Or at least
> there isn't on Solaris.
Just make the change Solaris specific, that's all !
Daniel
--
Daniel Veillard | Red Hat Network https://rhn.redhat.com/
veillard redhat com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]