deepak singh-4 wrote:
>
> Use apr, apr-util, expat, log4cxx libraries compiled with -fPIC flag.
> It works in my case.
>> I'l try to fire up a copy of CentOS 5 x64 this weekend.
>>
>> Did it occur during the unit tests or one of the sample applications, or
>> in
>> some other context?
>>
>
I had rewritten a multi-threaded application to test the threadsafetyness of
the log4cxx and got that error. But after rebuilding it with the CFLAGS
option you suggested, the error went away. But I did notice that after
building the log4cxx library, and did a 'make check', it seem to have failed
some of the tests:
SUCCESS
domtestcase : SUCCESS
xmllayouttest : SUCCESS
xmllayouttestcase : SUCCESS
Failed Tests Total Fail Failed %
===================================================
minimumtestcase 2 1 50.00%
patternlayouttest 14 2 14.29%
make[3]: *** [run-unittest] Error 1
Scrolling back to the test printout:
syslogwritertest : -log4cxx: Cannot get information about host:
unknown.invalid
log4cxx: Could not find unknown.invalid. All logging will FAIL.
log4cxx: Cannot get information about host: unknown.invalid
SUCCESS
timezonetestcase : SUCCESS
transcodertestcase : SUCCESS
hierarchytest : SUCCESS
hierarchythresholdtestcase: SUCCESS
l7dtestcase : SUCCESS
leveltestcase : SUCCESS
loggertestcase : -log4cxx: No appender could be found for logger (x).
log4cxx: Please initialize the log4cxx system properly.
SUCCESS
minimumtestcase : |Files [output/filtered] and [witness/ttcc] differ on
line 1
One reads: [14 Jul 2010 16:22:41,470 [main] FATAL ERR - Message 0].
Other reads:[ [main] FATAL ERR - Message 0].
--------------------------------
Contents of output/filtered:
1 : 14 Jul 2010 16:22:41,470 [main] FATAL ERR - Message 0
2 : 14 Jul 2010 16:22:41,470 [main] ERROR ERR - Message 1
3 : 14 Jul 2010 16:22:41,470 [main] FATAL INF - Message 2
4 : 14 Jul 2010 16:22:41,470 [main] ERROR INF - Message 3
5 : 14 Jul 2010 16:22:41,470 [main] WARN INF - Message 4
6 : 14 Jul 2010 16:22:41,470 [main] INFO INF - Message 5
7 : 14 Jul 2010 16:22:41,470 [main] FATAL INF.UNDEF - Message 6
8 : 14 Jul 2010 16:22:41,470 [main] ERROR INF.UNDEF - Message 7
9 : 14 Jul 2010 16:22:41,470 [main] WARN INF.UNDEF - Message 8
10 : 14 Jul 2010 16:22:41,470 [main] INFO INF.UNDEF - Message 9
11 : 14 Jul 2010 16:22:41,470 [main] FATAL INF.ERR - Message 10
12 : 14 Jul 2010 16:22:41,470 [main] ERROR INF.ERR - Message 11
13 : 14 Jul 2010 16:22:41,470 [main] FATAL INF.ERR.UNDEF - Message 12
14 : 14 Jul 2010 16:22:41,470 [main] ERROR INF.ERR.UNDEF - Message 13
15 : 14 Jul 2010 16:22:41,470 [main] FATAL DEB - Message 14
16 : 14 Jul 2010 16:22:41,470 [main] ERROR DEB - Message 15
17 : 14 Jul 2010 16:22:41,470 [main] WARN DEB - Message 16
18 : 14 Jul 2010 16:22:41,470 [main] INFO DEB - Message 17
19 : 14 Jul 2010 16:22:41,470 [main] DEBUG DEB - Message 18
20 : 14 Jul 2010 16:22:41,470 [main] FATAL UNDEF - Message 19
21 : 14 Jul 2010 16:22:41,470 [main] ERROR UNDEF - Message 20
22 : 14 Jul 2010 16:22:41,470 [main] WARN UNDEF - Message 21
23 : 14 Jul 2010 16:22:41,470 [main] INFO UNDEF - Message 22
24 : 14 Jul 2010 16:22:41,470 [main] DEBUG UNDEF - Message 23
25 : 14 Jul 2010 16:22:41,470 [main] INFO INF - Messages should bear
numbers 0 through 23.
--------------------------------
Contents of witness/ttcc:
1 : [main] FATAL ERR - Message 0
2 : [main] ERROR ERR - Message 1
3 : [main] FATAL INF - Message 2
4 : [main] ERROR INF - Message 3
5 : [main] WARN INF - Message 4
6 : [main] INFO INF - Message 5
7 : [main] FATAL INF.UNDEF - Message 6
8 : [main] ERROR INF.UNDEF - Message 7
9 : [main] WARN INF.UNDEF - Message 8
10 : [main] INFO INF.UNDEF - Message 9
11 : [main] FATAL INF.ERR - Message 10
12 : [main] ERROR INF.ERR - Message 11
13 : [main] FATAL INF.ERR.UNDEF - Message 12
14 : [main] ERROR INF.ERR.UNDEF - Message 13
15 : [main] FATAL DEB - Message 14
16 : [main] ERROR DEB - Message 15
17 : [main] WARN DEB - Message 16
18 : [main] INFO DEB - Message 17
19 : [main] DEBUG DEB - Message 18
20 : [main] FATAL UNDEF - Message 19
21 : [main] ERROR UNDEF - Message 20
22 : [main] WARN UNDEF - Message 21
23 : [main] INFO UNDEF - Message 22
24 : [main] DEBUG UNDEF - Message 23
25 : [main] INFO INF - Messages should bear numbers 0 through 23.
\Line 112: Compare::compare(FILTERED, witness) was expected to be true, was
false.
FAILED 1 of 2
Contents of witness/patternLayout.5:
1 : [main] DEBUG atternLayoutTest - Message 0
2 : [main] DEBUG root - Message 0
3 : [main] INFO atternLayoutTest - Message 1
4 : [main] INFO root - Message 1
5 : [main] WARN atternLayoutTest - Message 2
6 : [main] WARN root - Message 2
7 : [main] ERROR atternLayoutTest - Message 3
8 : [main] ERROR root - Message 3
9 : [main] FATAL atternLayoutTest - Message 4
10 : [main] FATAL root - Message 4
-Line 217: Compare::compare(FILTERED,
LOG4CXX_FILE("witness/patternLayout.5")) was expected to be true, was false.
FAILED 2 of 14
propertyconfiguratortest: SUCCESS
I downloaded apache-log4cxx-0.10.0.tar.gz and built it on a 64 bit on a Red
Hat Enterprise Linux Server release 5.5 (Tikanga). Anyone know why the
check is failing?
--
View this message in context:
http://old.nabble.com/log4cxx-0.10.0%3A-Fix-for-64-bit-only-thread-safety-bug-in-ObjectPtrBase-tp21504865p29166444.html
Sent from the Log4cxx - Dev mailing list archive at Nabble.com.
