On 12/11/06, Charles Tuckey <[EMAIL PROTECTED]> wrote:
[This reply was received from Curt Arnold via private email.]
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.
I have noticed the problem on both FC5, 32 bit and FC6 64 bit systems.
I no longer have access to the FC5 system (hard drive failure) but on
the FC6 system I am using:
gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)
/usr/lib64/libapr-1.so.0.2.7
/usr/lib64/libaprutil-1.so.0.2.7
log4cxx HEAD version of 061113
I didn't do anything special to build log4cxx; I just followed the
instructions in INSTALL.
I believe the seg fault is occurring because the pango library is
accessing apr functions from the log4cxx library instead of the shared
apr libraries.
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.
I did look at the configure script to see if there was a way to
specify shared libraries but I didn't think to look at the ant
scripts. I will try this.
[From Curt Arnold]
--
Regards,
Charlie
