Compiling log4cxx on Win32

[Shlomi Levi <ls...@gmail.com>]

When compiling log4cxx using VS .NET 2003, The test application fails.

 


Build transcript by ant:
++++++++++++++++++

Buildfile: build.xml

os-detect:

win-init:

mac-init:

unix-init:

init:

build-apr:

get-apr-src:

untar-apr-src:

os-detect:

win-init:

unix-init:

init:

configure-check:

unix-configure:

win-configure:

configure:

build:
       [cc] Starting dependency analysis for 65 files.
       [cc] 65 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

build-apriconv:

get-apriconv-src:

untar-apriconv-src:

os-detect:

win-init:

unix-init:

init:

configure-check:

unix-configure:

win-configure:

configure:

build-lib:
       [cc] Starting dependency analysis for 9 files.
       [cc] 9 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

build-aprutil:

get-aprutil-src:

untar-aprutil-src:

os-detect:

win-init:

unix-init:

init:

configure-check:

unix-configure:

win-configure:

configure:

build:
       [cc] Starting dependency analysis for 42 files.
       [cc] 42 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

build:
       [cc] Starting dependency analysis for 102 files.
       [cc] 102 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

build-shortsocketserver:
       [cc] Starting dependency analysis for 2 files.
       [cc] 2 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.
       [cc] Starting link

build-cppunit:

get-cppunit-src:

untar-cppunit-src:

os-detect:

win-init:

unix-init:

init:

configure-check:

unix-configure:

win-configure:

configure:

build:
       [cc] Starting dependency analysis for 49 files.
       [cc] 49 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

build-unittest:
       [cc] Starting dependency analysis for 74 files.
       [cc] 74 files are up to date.
       [cc] 0 files to be recompiled from dependency analysis.
       [cc] 0 total files to be compiled.

run-unittest:

     [exec] This application has requested the Runtime to terminate it in an
unusual way.
     [exec] Please contact the application's support team for more
information.
     [exec] Result: 3

     [exec] This application has requested the Runtime to terminate it in an
unusual way.
     [exec] Please contact the application's support team for more
information.
     [exec] Result: 3

     [exec] This application has requested the Runtime to terminate it in an
unusual way.
     [exec] Please contact the application's support team for more
information.
     [exec] Result: 3
    [mkdir] Created dir:
G:\cyghome\lshl\log4cxx\logging-log4cxx\build\debug\shared\output
     [copy] Copying 1 file to
G:\cyghome\lshl\log4cxx\logging-log4cxx\build\debug\shared

     [exec] This application has requested the Runtime to terminate it in an
unusual way.
     [exec] Please contact the application's support team for more
information.

BUILD FAILED
G:\cyghome\lshl\log4cxx\logging-log4cxx\build.xml:967: exec returned: 3

Total time: 42 seconds

10x,
Shlomi

Re: Compiling log4cxx on Win32

[Curt Arnold <ca...@apache.org>]

On Apr 16, 2005, at 5:03 PM, Shlomi Levi wrote:

> When compiling log4cxx using VS .NET 2003, The test application fails.
>

The current CVS HEAD is broken on Windows, see 
http://marc.theaimsgroup.com/?l=log4cxx-dev&m=111233291509541&w=2.  
I've finished and filed my taxes and will return to log4cxx development 
next weekend and that is at the top of my log4cxx task list.

Until I have a chance to rework that code, you may want to pull a 
snapshot from before 31 March (can't find my CVS book at the moment to 
give you the syntax).