public inbox for
 help / color / mirror / Atom feed
From: Gary Benson <>
Subject: merged-libs-branch
Date: Tue, 30 Sep 2003 11:04:00 -0000	[thread overview]
Message-ID: <> (raw)


The merged-libs-branch in xerces, xalan and mx4j contains fixes for
broken circular linking which makes dlopen() fail on some of the
libraries in these packages.

The problem was that mx4j, for example, has two class heirachies: and mx4j, being the interface and
mx4j being the implementation.  For this to be linked 'correctly'
lib-javax-management must be linked to lib-mx4j and lib-mx4j
must be linked to lib-javax-management.

While it's theoretically possible to do this it isn't recommended; I
could just feel Uli crossing himself as he answered my emails ;) In
RHUG HEAD this problem is avoided by not linking lib-j-m to lib-mx4j,
and linking lib-mx4j to executables that need it.

In merged-libs-branch I moved the classes around so that there were no
circular links.  In xerces the classes from org.w3c.dom,
org.apache.xerces and org.apache.xml.serialize were moved into
lib-javax-xml-parsers; xalan, the classes from org.apache.xml and
org.apache.xpath were moved into lib-org-apache-xalan; and in mx4j the
classes from mx4j were moved into lib-javax-management.  Dummy
libraries were created for org.w3c.dom, org.apache.xerces,
org.apache.xml.serialize, org.apache.xml, org.apache.xpath and mx4j;
the dummies are empty libraries that link to the libraries that
actually contain their classes.

It all seems to work beautifully.  Anyone mind if I merge the changes
into HEAD?


[ ][ GnuPG 85A8F78B ][ ]

             reply	other threads:[~2003-09-30 11:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 11:04 Gary Benson [this message]
2003-09-30 15:22 ` merged-libs-branch Anthony Green
2003-09-30 15:41   ` merged-libs-branch Gary Benson
2003-10-01 21:39 ` merged-libs-branch Tom Tromey
2003-10-02  8:42   ` merged-libs-branch Gary Benson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).