[Mono-list] Mono CVS build issue

[Ricardo Kirkner]

Andrew Birkett wrote:

>On Thu, 2002-09-12 at 23:27, Ricardo Kirkner wrote:
>
>>I am sorry, but i did not understand what you sayed.  Could you please 
>>explain it again to me? Why does the makefile generate those zero sized 
>>files?  How can I do to get the files correctly compiled?
>>
>
>When you build 'mono', it hopes that you will also have the 'mcs'
>project checked out and already built.  The dlls which you listed are
>built as part of the mcs project, and so you need to check out and build
>the 'mcs' project first.  Once you have done that you can build the
>'mono' project and it will pick up the dlls from ../mcs/class/lib.
>
>(If you're starting from scratch, you will need to install a prebuilt
>version of mono/mcs in order to build the class libraries in the first
>place - it's a chicken and egg situation).
>
>There is an easier hacky method.  Just check out 'mono', build it and
>install it.  Download one of the prebuilt tarballs (like mono-0.15) and
>copy the dlls from the tarball over the zero-sized dlls from your mono
>build.  This will give you an up-to-date jit with older class
>libraries.  It may not always work though.
>
>Andrew
>- www.nobugs.org -
>
>
>
>_______________________________________________
>Mono-list maillist  -  Mono-list@ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-list
>
I tried that, but unsuccessfully... I compiled mono and mcs for source, 
both without problems. Then I checked mono and mcs from cvs, and when I 
tried to compile mcs, I got the  following (it is an error similar to 
the one I got before):

** (process:31269): WARNING **: cant resolve internal call to 
"System.Reflection.Assembly::get_location()" (tested without signature also)

Your mono runtime and corlib are out of sync.
etc etc

Of course, this prevents me from even triyng to compile mono (because yo 
said I need to compile mcs before mono, when I do from cvs)

Ricardo