Hmm, ignore this for now. It looks like this might be specific to mono
on linux/ppc, since it seems to work fine on i386.

Jeroen

On Sun, 2004-06-27 at 10:45 +0200, Jeroen Zwartepoorte wrote:
> Hi,
> 
> I just built CVS HEAD of NAnt on a clean Fedora Core 2 install with the
> Release Candidate of Mono. After succesfully builing NAant, when i try
> to use it, i get the following error/exceptions:
> 
> [EMAIL PROTECTED] monodevelop]$ nant
> Compat mode: the request from /home/jeroen/nant/bin/log4net.dll to load
> System.Data was remapped (http://www.go-mono.com/remap.html)
> Compat mode: the request from /home/jeroen/nant/bin/log4net.dll to load
> System.Web was remapped (http://www.go-mono.com/remap.html)
> NAnt 0.85 (Build 0.85.1596.0; mono-1.0.unix; nightly; 5/15/2004)
> Copyright (C) 2001-2004 Gerry Shaw
> NAnt Team
> 
> Compat mode: the request from /home/jeroen/nant/bin/lib/mono/1.0/NDoc.
> Core.dll to load System.Windows.Forms was remapped
> (http://www.go-mono.com/remap.html)
> 
> Unhandled Exception: System.NullReferenceException: Object reference not
> set to an instance of an object
> 
> Unhandled Exception: System.NullReferenceException: Object reference not
> set to an instance of an object
> BUILD FAILED
> 
> The current runtime framework 'mono-1.0' is not correctly configured in
> the NAnt configuration file.
>     Unable to locate 'mono' module using pkg-config. Download the Mono
> development packages from http://www.go-mono.com/downloads.
> 
> For more information regarding the cause of the build failure, run the
> build again in debug mode.
> 
> Try 'nant -help' for more information
> 
> 
> The two NullReferenceException seem to occur shortly after the
> outputThread and errorThread are started in ExternalProgramBase.cs
> (ExecuteTask method). If i comment those lines and the following Join
> ()'s out, the exceptions are no longer thrown...
> 
> However, there's still the bug where somehow nant thinks mono is not
> installed (running pkg-config --variable=prefix mono works fine). This
> is on the same machine where the nightly build from june 19th works
> fine. So i'm guessing this is either related to the latest mono release
> candidate or a bug in nant which has appeared in the mean time.
> 
> Any ideas?
> 
> My overall impressions atm are that NAnt is far from ready to be used
> with mono under Linux atm (which is really too bad) :/
> 
> Jeroen
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Nant-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nant-users
> 



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to