[Mono-devel-list] [Pkg-mono-devel] Re: [GUMP at brutus]: ant/test-ant failed (fwd)
Adam R. B. Jack
ajack at apache.org
Wed Aug 18 16:56:42 EDT 2004
Can anybody here help, I've had no response on the debian list. Basically the mono installation appeared smooth, however we see this problem.
Thanks in advance.
regards
Adam
--
Have you Gump'ed your code today?
http://gump.apache.org
---------- Forwarded message ----------
Date: Tue, 10 Aug 2004 22:14:34 -0700 (PDT)
From: Adam R. B. Jack <ajack at apache.org>
To: pkg-mono-devel at lists.alioth.debian.org
Subject: [Pkg-mono-devel] Re: [GUMP at brutus]: ant/test-ant failed (fwd)
Hi
I believe issues with running Mono (installed via Debian package) were to be
reported here also. These tests (within Ant's dotnet work) work on other Mono
installs, but fail here. Is there enough information to look into this?
Thanks in advance.
regards
Adam
--
Have you Gump'ed your code today?
http://gump.apache.org
---------- Forwarded message ----------
Date: Tue, 10 Aug 2004 12:12:30 +0200
From: Stefan Bodewig <bodewig at apache.org>
Reply-To: Ant Developers List <dev at ant.apache.org>
To: dev at ant.apache.org
Subject: Re: [GUMP at brutus]: ant/test-ant failed
On Tue, 10 Aug 2004, Stefan Bodewig <bodewig at apache.org> wrote:
> ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v
probe_for_apps:
Property ${env.Path} has not been set
[available] Found: ilasm in /usr/bin
[echo] ilasm.found=true
Property ${env.Path} has not been set
[available] Unable to find csc
[available] Unable to find csc.exe
[available] Unable to find csc.exe
Property ${csc.found} has not been set
[echo] csc.found=${csc.found}
Property ${env.Path} has not been set
[available] Unable to find vbc
[available] Unable to find vbc.exe
[available] Unable to find vbc.exe
Property ${vbc.found} has not been set
[echo] vbc.found=${vbc.found}
Property ${env.Path} has not been set
[available] Unable to find vjc
[available] Unable to find vjc.exe
[available] Unable to find vjc.exe
Property ${jsharp.found} has not been set
[echo] jsharp.found=${jsharp.found}
[available] Found: mcs in /usr/bin
[echo] mcs.found=true
[available] Found: ilasm in /usr/bin
[echo] mono.ilasm.found=true
Property ${env.Path} has not been set
[available] Unable to find ildasm
[available] Unable to find ildasm.exe
[available] Unable to find ildasm.exe
Property ${ildasm.found} has not been set
[echo] ildasm.found=${ildasm.found}
[echo] dotnetapps.found=true
[available] Found: mono in /usr/bin
Override ignored for property mono.executable
init:
[mkdir] Created dir:
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/build
validate_csc:
testCSC-Mono:
[csc] working from source directory
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional
[csc]
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs
is out of date
[csc]
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs
is out of date
[csc] compiling 2 files
Executing 'mcs' with arguments:
'/nologo'
'/debug+'
'/optimize-'
'/out:/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/build/ExampleCsc.exe'
'/target:exe'
'/nostdlib-'
'/warn:3'
'/fullpaths'
'/incremental-'
'/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs'
'/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs'
The ' characters around the executable and arguments are
not part of the command.
[csc] Compilation succeeded
[csc] Unhandled Exception: System.NullReferenceException: Object
reference not set to an instance of an object
[csc] ** ERROR **: file critical-sections.c: line 89
(DeleteCriticalSection): assertion failed: (ret == 0)
[csc] aborting...
BUILD FAILED
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155:
csc returned: 129
at
org.apache.tools.ant.taskdefs.optional.dotnet.NetCommand.runCommand(NetCommand.java:293)
This looks fine from the Ant side and seems to be an issue with the
Mono installation (as expected). Compilation succeeds but mono (the
VM running the compiler) fails with an error I've never seen before.
Do we already have a Mono 1.0.1 available for Debian?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at ant.apache.org
For additional commands, e-mail: dev-help at ant.apache.org
_______________________________________________
Pkg-mono-devel mailing list
Pkg-mono-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-mono-devel
More information about the Mono-devel-list
mailing list