[Mono-devel-list] System.NullReferenceException during MCS build

Paolo Molaro lupus at ximian.com
Mon Jun 23 05:37:34 EDT 2003

Thanks for posting the same mail to two different lists,
I was certainly going to miss it if it wasn't for that!

On 06/22/03 Sebastian Bergmann wrote:
>   1.) I downloaded
>         http://www.go-mono.com/archive/mono-0.24.tar.gz
>       and installed it to
>         /usr/local/mono
>   2.) I checked out the current CVS version of mono and installed it to
>         /usr/local/mono

This is the wrong step: to use mono from cvs you also need the base
assemblies from cvs (corlib for sure, sometimes also System.dll).
So, before installing the mono cvs module, you need to bootstrap
corlib in the mcs module. As soon as you build corlib, the build system
uses it to build the rest of the assemblies, so you'll get an error at
that point since you'll be using a new corlib and an old mono runtime.
At this point, instead of panicking, you can build and install the mono
module and install the just built corlib.dll. Now, you have a matching
corlib and runtime and you can continue building the mcs module.
People that don't follow the build process and install the runtime
first can grab a monocharge from http://www.gotmono.com/sapians/jackson/:
the tarball contains the assemblies built from a current cvs and so can
be used once you have overwritten your working mono runtime with a
runtime from cvs without updating the base assemblies as well.



lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Mono-devel-list mailing list