I bypassed use of the Makefile and was able to successfully build nant
by directly issuing:
mono bin/NAnt.exe -f:NAnt.build build
Curiously, this is identical to the command that is invoked by running
"make" under a non-WinNT environment.
I'm still uncertain why it was segfaulting under make, as I have a
fairly standard x86 Gentoo system configuration with kernel 2.6.8,
although I did compile the Native Posix Threading Library into glibc
(and of course re-compiled all affected packages). There doesn't seem
to be any rationale (other than convention) for using "make" as a
front-end to NAnt.exe for the build. Perhaps this method should be
scrapped in favor of .bat and .sh scripts?
Anyhow, having successfully built nant I attempted a make-less install
in a similar fashion:
mono bin/NAnt.exe install -D:install.prefix=/usr
Everything was going well until I encountered:
[exec] self-userdoc:
[exec]
[exec] [ndoc] Initializing...
[exec] [ndoc] Merging XML documentation...
[exec] [ndoc] Building mapping...
[exec] [ndoc] Creating Task Index Page...
[exec] [ndoc] Creating Type Index Page...
[exec] [ndoc] Creating Filter Index Page...
[exec] [ndoc] Creating Function Index Page...
[exec] [ndoc] Generating Task Documents...
-- whereupon ndoc proceeded to munch 100% CPU for over an hour. Mind
you, this is under a 2 GHz Athlon XP and 1 GB DDR400 RAM. I allowed
the process to continue (though not with infinite patience), and
luckily the installation finally completed and nant appears to be
functional. I'm wondering if the culprit is use of the pre-built ndoc
binary under mono. If I get some time later I'll try swapping it with
a locally built ndoc to see if that makes any difference.
On Tue, 30 Nov 2004 16:41:25 -0600, J. Christopher Six
<[EMAIL PROTECTED]> wrote:
> I have mono 1.0.4 installed under Gentoo and receive an error when
> performing "make" on the nant 0.85-rc1 sources:
>
> [nant]
> /home/bitflux/Applications/nant-0.85-rc1/src/NAnt.Compression/NAnt.Compression.build
> build
> make: *** [build-nant] Segmentation fault
>
> NAnt.Compression.build contains a workaround for a bug that was
> supposedly fixed in mono a couple of months ago and I suspect this may
> be related to my problem. If this is the case, please let me know if
> there's a workaround for the workaround.
>
> -- J. Christopher Six
>
--
J. Christopher Six
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
