On May 21, 2005, at 5:03 AM, J�rgen F. Kilian wrote:

Hi,

I tried to build (using ant) log4cxx (cvs HEAD) under w32 for VC6.

The compilation seems to work but then at least one of the tests fails (see trace further down).

Any ideas how this could be fixed?
Would anyone be able to provie me just the binaries (.dll .lib) which could be used on w32 with VC6 and VS 2003?


     [exec] 1) test: PatternParserTestCase::testNewWord (E)
     [exec] uncaught exception of unknown type


     [exec] 2) test: PatternParserTestCase::testNewWord2 (E)
     [exec] uncaught exception of unknown type


These tests fail on VC6, but pass on VC 7 and later and pass on other platforms. I have not been able to get any useful debugging information to indicate what is going wrong with VC6. Any insight that might unravel what is going on with VC6 would be helpful.

The scenario that is failing involves user-added format specifiers (for example, %foo) to the PatternLayout which would not affect typical usage of log4cxx.


[exec] 3) test: DateTimeDateFormatTestCase::test1 (F) line: 96 N:\src\logging-log4cxx\tests\src\helpers \datetimedateformattestcase.cpp
     [exec] equality assertion failed
     [exec] - Expected: 02 Jan 2004 00:00:00,000
     [exec] - Actual  : 0? Jan ???? 0?:0?:0?,00?


....

[exec] 16) test: CachedDateFormatTestCase::test17 (F) line: 545 N:\src\logging-log4cxx\tests\src\helpers \cacheddateformattestcase.cpp
     [exec] equality assertion failed
     [exec] - Expected: 00:00:00,000 00:00:00,000
     [exec] - Actual  : 0?:0?:0?,00? 0?:0?:0?,00?


I've seen similar symptoms with locale related issues, but not affecting so many tests. I'm not able to investigate at the moment, but will after complete a few critical tasks. All these involve date formatting.

Would anyone be able to provie me just the binaries (.dll .lib) which could be used on w32 with VC6 and VS 2003?

You've build the VC6 binaries, they are just questionable with date formatting (significant) and user-added format specifiers. Building using VS 2003 should remove the issue with user-added format specifiers. Just treat date formats as a little questionable for a few days.

Reply via email to