[This reply was received from Curt Arnold via private email.]
On 12/11/06, Charles Tuckey <[EMAIL PROTECTED]> wrote:
Hi,
I am using log4cxx in a program that also uses libpangoft2
(/usr/lib64/libpangoft2-1.0.so.0.1400.8) - running on Fedora Core 6.
I am building log4cxx from CVS. The build integrates functions from
apr, apr-util and expat directly into the log4cxx library. These
functions conflict with what pangoft2 is expecting and my program seg
faults. I built log4cxx without the apr functions and I don't get the
seg fault.
My question is why the apr functions are automatically built-in to
log4cxx? Shouldn't a check be made to see if they already exist as a
shared library and, if so, use the existing shared libraries instead?
--
Regards,
Charlie
I have not had reports of errors due to between conflicts between the
APR instance used by log4cxx and APR in use by the calling
application. Any specifics on compiler, platform, stack trace,
failure scenario, and what made you think it was a conflict between
APR versions would be appreciated. No APR resource should be exposed
through log4cxx, so the calling program should be unaware that APR is
being used by log4cxx internally.
You can build log4cxx to use a shared instance of APR and APR-util by
specifying
ant -Dapr.lib.type=shared -Daprutil.lib.type=shared
Likely a way to do it on the autotools build, but don't know it
offhand.
[From Curt Arnold]
