On Feb 16, 2007, at 10:30 AM, Sander Temme wrote:
On Feb 16, 2007, at 7:46 AM, Gert Driesen wrote:
You either need a more recent version of Mono, or I could modify
NAnt to
allow it to compile on that version of Mono. I don't know if you'd
consider
using a nightly build (or any non-released version) of NAnt.
I'll look into upgrading Mono on Clarus. Using nightly builds is
not what Gump is about: it merely tries to compile the latest,
perhaps-not-so-greatest of everything, satisfying dependencies with
the development trunk of that moment. It uses that to find out
when/where things break at the earliest possible moment.
Looking at the code that fails on Mono, it looks like the problem is
that Mono is detected as supporting .NET 2 but is missing a framework
method expected to be there. I'm guessing that it would either
successfully compile on something earlier that was not detected
as .NET 2 or something later that had the missing method. Do you
know of a later version of Mono that NAnt does build on? Updating
the Mono version seems to be the right direction as I'm guessing .NET
1 is slowly fading (though I'm not in that world very much).
As for vmgump, previous statements suggest it is pretty precarious
and I doubt that the benefit would be worth the risk to touch Mono on
it until the next major externally driven change. For log4net, as
long as we had NAnt and log4net building on Claris and ideally with
nag messages sent to the appropriate mailing lists, things would be
good.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
