[Mono-devel-list] Compiling from CVS

[Robert Shade]

That's ok.  It was trying to copy class libraries from the runtime
subdirectory, however at that point the runtime has been installed.  So,
if you only installed monolite or you wish to do a full compiler and class
library build, go ahead and run the "make fullbuild" now.  Everything
should work correctly.

rob

> So I've done what you said.  And when I run "make" within mono after
> copying over the monolite files I find this in the end of its reuslts:
>
>   cp: cannot stat `../../mcs/class/lib/libgdiplus.dll.so': No such file
> or directory
>
> So for the sake of humility, I continued as the previous didn't not
> generate an error, but "make install" does.
>
> =========
> /usr/bin/install: cannot stat `./libgdiplus.dll.so': No such file or
> directory
> make[2]: *** [install-assembliesDATA] Error 1
> make[2]: Leaving directory `/usr/local/Mono/src/mono-cvs/mono/runtime'
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory `/usr/local/Mono/src/mono-cvs/mono/runtime'
> make: *** [install-recursive] Error 1
> =========
>
> Any suggestions?
>
> ~ Matthew
>
> On Wed, 2003-11-19 at 01:44, Robert Shade wrote:
>> Go to http://go-mono.com/daily/ and download the latest monocharge
>> (monolite if you are going to go back and recompile mcs and the class
>> libraries) and copy the contents to the runtime subdirectory of mono.
>> Overwrite whatever may already be there.
>>
>> Then, just do a make with no arguments and then make install.
>>
>> rob
>>
>> PS.  fullbuild is supposed to get around this by using the old runtime
>> and mcs to compile the new mcs before the new runtime is installed.
>> However, the newer runtime must already be installed on your machine
>> and is why it is not working.
>>
>> After you do the above, fullbuild should work properly.
>>
>>
>> On Nov 19, 2003, at 1:16 AM, Met @ Uber wrote:
>>
>> > On Wed, 2003-11-19 at 00:48, Met @ Uber wrote:
>> >> I keep finding conflicting instructions on how to install Mono via
>> >> CVS.
>> >> The Wiki says something different than the README's.  So what's
>> >> correct?
>> >>
>> >> I'm running Mono-0.28 (release) from source.  I have checked out the
>> >> latest from CVS (not through Anon in case that's a problem), and have
>> >> tried two things:
>> >>
>> >>   1) The Mono/MCS Install & Readme directions
>> >>       cd mono
>> >>       ./autogen --prefix=/usr/local
>> >>       make fullbuild
>> >>
>> >>>> errors out with ::
>> >>>>   Your mono runtime and corlib are out of sync.
>> >>>>   Corlib is: mscorlib
>> >>
>> >>   2) Mono Wiki directions
>> >>       cd mcs
>> >>       ./autogen --prefix=/usr/local
>> >>       make
>> >>
>> >>>> errors out with ::
>> >>>>   Your mono runtime and corlib are out of sync.
>> >>>>   Corlib is: mscorlib
>> >>
>> >>       make install (etc etc etc)
>> >>
>> >> I know I'm the XXX person to ask, but I don't know.  Documentation
>> >> should be unified, and I should be more willing to hit my head on the
>> >> wall figuring this out.
>> >>
>> >> Help ?
>> >>
>> >> Thanks in advance,
>> >>
>> >> ~ Matthew
>> >
>> > I'm tired, so forgive me.
>> >
>> > I also tried :: make PROFILE="atomic" :: within MCS.  No such luck,
>> > generated errors.
>> > ===
>> > mcs /nowarn:649 /nowarn:169 -d:INSIDE_CORLIB  /lib:/usr/local/lib -g
>> > /noconfig /unsafe /nostdlib /target:library
>> > /out:../../class/lib/mscorlib.dll
>> @../../build/deps/corlib.dll.response
>> > System.Security.Cryptography/HMACSHA1.cs(110) error CS0246: Cannot
>> > find
>> > type `HMAC'
>> > ===
>> >
>> > I'm sure there's something I'm missing... and its probably looking
>> > directly at me laughing
>> >
>> > ~ Matthew
>> >
>> > _______________________________________________
>> > Mono-devel-list mailing list
>> > Mono-devel-list at lists.ximian.com
>> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>
>