You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-user@logging.apache.org by Torsten Wiebesiek <to...@grecon.de> on 2007/08/29 15:12:01 UTC
Build on Win32 broken
Hi,
I just tried to compile the latest svn snapshot of log4cxx on my Windows
XP system. Unfortunately, it failed.
The last output of ant was:
> win-configure:
>
> configure:
> [echo] Configuring with has.wchar_t=1
> [echo] Configuring with has.wcout=1
> [echo] Configuring with logchar_type=wchar_t
>
> build:
> [cc] Starting dependency analysis for 144 files.
> [cc] 144 files are up to date.
> [cc] 0 files to be recompiled from dependency analysis.
> [cc] 0 total files to be compiled.
> [cc] Starting link
> [cc] link: extra operand "/DLL"
> [cc] "link --help" gives more information
>
> BUILD FAILED
> C:\Project\SuperScanII\extern\log4cxx\build.xml:615: link failed
> with return code 1
I then tried to compile it with Microsofts Visual Studio 2005. I
created the project files with ant build-projects-vs8 and
opened/compiled the project files following results:
1. msvc8\apr success :-)
2. msvc8\aprutil success :-)
3. msvc8\cppunit success :-)
4. msvc8\log4cxx failure :-(
1>writerappender.cpp
1>xmllayout.cpp
1>xmlsocketappender.cpp
1>Code is generated...
1>Linking...
1>LINK : fatal error LNK1181: Cannot open input file ".obj".
Can anyone help me, getting log4cxx working on Windows XP with
Visual Studio 2005?
Regards,
Torsten
Re: Build on Win32 broken
Posted by Torsten Wiebesiek <to...@grecon.de>.
> Thanks a lot. Now log4cxx compiles. Unfortunatly, the unit test fail.
> I have copied the last lines of ant output at the end of this file.
>
> Is this again a problem with my environment? Or is it a problem with
> log4cxx?
Well, acutally, it was again a problem with my environment. Putting the
my GnuWin32 tools to the path broke compiling log4cxx cause there was
a wrong link command in the path. The unit tests failed failed, cause
the sed command wasn't in the path after removing the GnuWin32 tools
from the path.
Now all works fine! :-)
Torsten
AW: Build on Win32 broken
Posted by Torsten Wiebesiek <to...@grecon.de>.
> > I just tried to compile the latest svn snapshot of log4cxx on my
> > Windows
> > XP system. Unfortunately, it failed.
> >
> > The last output of ant was:
> >
> > > win-configure:
> > >
> > > configure:
> > > [echo] Configuring with has.wchar_t=1
> > > [echo] Configuring with has.wcout=1
> > > [echo] Configuring with logchar_type=wchar_t
> > >
> > > build:
> > > [cc] Starting dependency analysis for 144 files.
> > > [cc] 144 files are up to date.
> > > [cc] 0 files to be recompiled from dependency analysis.
> > > [cc] 0 total files to be compiled.
> > > [cc] Starting link
> > > [cc] link: extra operand "/DLL"
> > > [cc] "link --help" gives more information
> > >
> > > BUILD FAILED
> > > C:\Project\SuperScanII\extern\log4cxx\build.xml:615: link failed
> > > with return code 1
> >
>
> That appears like you have Cygwin or MinGW in the Path ahead of
> Microsoft Visual C++. Both have a program named "link", but MS link
> would never ask you to ask for more help using "--help" Run
> vcvars32.bat again to put VC in the front of the path and try again.
Thanks a lot. Now log4cxx compiles. Unfortunatly, the unit test fail.
I have copied the last lines of ant output at the end of this file.
Is this again a problem with my environment? Or is it a problem with
log4cxx?
> > I then tried to compile it with Microsofts Visual Studio 2005. I
> > created the project files with ant build-projects-vs8 and
> > opened/compiled the project files following results:
> >
> > 1. msvc8\apr success :-)
> > 2. msvc8\aprutil success :-)
> > 3. msvc8\cppunit success :-)
> > 4. msvc8\log4cxx failure :-(
> >
> > 1>writerappender.cpp
> > 1>xmllayout.cpp
> > 1>xmlsocketappender.cpp
> > 1>Code is generated...
> > 1>Linking...
> > 1>LINK : fatal error LNK1181: Cannot open input file ".obj".
> >
>
> Looks like the project has an embedded bogus file name. You could
> open the .vcproj file with a text editor (select Open As Text from
> the File Open dialog should do it) and then look for ".obj" or
> similar and remove it and see what happens.
Couldn't find anything like that. At least no suspicious line containing
"obj".
Best regards,
Torsten
And here's the ant output:
> run-defaultinit-unittest:
> [mkdir] Created dir:
C:\Project\SuperScanII\extern\log4cxx\src\test\resources\output
> [copy] Copying 1 file to
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared
> [exec] .log4cxx: setFile(output/temp,false) call failed.
> [exec] log4cxx: IO Exception : status code = 720003
> [exec] log4cxx: No output stream or file set for the appender
named [D3].
> [exec]
> [exec]
> [exec]
> [exec] OK (1 tests)
> [exec]
> [exec]
> [copy] Copying 1 file to
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared
> [exec] .log4cxx: setFile(output/temp,false) call failed.
> [exec] log4cxx: IO Exception : status code = 720003
> [exec] log4cxx: No output stream or file set for the appender
named [D3].
> [exec]
> [exec]
> [exec]
> [exec] OK (1 tests)
> [exec]
> [exec]
> [delete] Deleting:
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared\log4cxx.proper
ties
> [delete] Deleting:
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared\log4j.properti
es
> [copy] Copying 1 file to
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared
> [copy] Copying 1 file to
C:\Project\SuperScanII\extern\log4cxx\target\debug\shared
> [exec] .
> [exec]
> [exec]
> [exec] OK (1 tests)
> [exec]
> [exec]
> [exec] .
> [exec]
> [exec]
> [exec] OK (1 tests)
> [exec]
> [exec]
> [exec] .
> [exec]
> [exec]
> [exec] OK (1 tests)
> [exec]
> [exec]
>
> clean-output:
>
> run-unittest:
> [exec] ............................Assertion failed: stat ==
APR_SUCCESS, file
C:\Project\SuperScanII\extern\log4cxx\src\test\cpp\util\
> transformer.cpp, line 212
> [exec]
> [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
> C:\Project\SuperScanII\extern\log4cxx\build.xml:1031: exec returned: 3
Re: Build on Win32 broken
Posted by Curt Arnold <ca...@apache.org>.
On Aug 29, 2007, at 8:12 AM, Torsten Wiebesiek wrote:
> Hi,
>
> I just tried to compile the latest svn snapshot of log4cxx on my
> Windows
> XP system. Unfortunately, it failed.
>
> The last output of ant was:
>
>> win-configure:
>>
>> configure:
>> [echo] Configuring with has.wchar_t=1
>> [echo] Configuring with has.wcout=1
>> [echo] Configuring with logchar_type=wchar_t
>>
>> build:
>> [cc] Starting dependency analysis for 144 files.
>> [cc] 144 files are up to date.
>> [cc] 0 files to be recompiled from dependency analysis.
>> [cc] 0 total files to be compiled.
>> [cc] Starting link
>> [cc] link: extra operand "/DLL"
>> [cc] "link --help" gives more information
>>
>> BUILD FAILED
>> C:\Project\SuperScanII\extern\log4cxx\build.xml:615: link failed
>> with return code 1
>
That appears like you have Cygwin or MinGW in the Path ahead of
Microsoft Visual C++. Both have a program named "link", but MS link
would never ask you to ask for more help using "--help" Run
vcvars32.bat again to put VC in the front of the path and try again.
> I then tried to compile it with Microsofts Visual Studio 2005. I
> created the project files with ant build-projects-vs8 and
> opened/compiled the project files following results:
>
> 1. msvc8\apr success :-)
> 2. msvc8\aprutil success :-)
> 3. msvc8\cppunit success :-)
> 4. msvc8\log4cxx failure :-(
>
> 1>writerappender.cpp
> 1>xmllayout.cpp
> 1>xmlsocketappender.cpp
> 1>Code is generated...
> 1>Linking...
> 1>LINK : fatal error LNK1181: Cannot open input file ".obj".
>
Looks like the project has an embedded bogus file name. You could
open the .vcproj file with a text editor (select Open As Text from
the File Open dialog should do it) and then look for ".obj" or
similar and remove it and see what happens.