[Mono-devel-list] Weird mcs assertion in make test in System.Data

[Paolo Molaro]

On 06/30/03 Gonzalo Paniagua Javier wrote:
> El dom, 29-06-2003 a las 21:19, Peter Williams escribió:
> > The problem ended up being due to the MONO_PATH environment variable not
> > being set when calling mcs.exe in my Makefiles. As I understand it we
> > should be able to build things without setting MONO_PATH, so do you have
> > any idea what the proper workaround would be?
> 
> We should define MONO_PATH to point to the mcs/class/lib directory or
> prepend that to the existing MONO_PATH content. That way the newly built
> libraries are used to compile the others as the building process goes
> on.

In the new build system, we want to de able to perform two different
type of builds:
*) a bootstrapping build where the newly compiled assemblies/compilers
are used in the next steps of the build
*) a normal build where all the stuff is built using the installed
libraries and compilers

In the first case we need MONO_PATH set as needed, in the second case it
should not be set. For running the tests, I assume MONO_PATH could
always be set to the just-built assemblies, though I don't understand
why it shouldn't work when it's unset, maybe there is some underlying
issue?

lupus

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