[Mono-devel-list] Compiling from CVS

Robert Shade rshade at dvsconsulting.com
Wed Nov 19 15:46:20 EST 2003

Yes :)

1.) make uninstall
2.) *** make sure you uninstalled any mono rpms *** (just thought of this
one... a mono rpm might still be installed in /usr and you're putting your
compiled mono in /usr/local.  The call to mcs would still go to the old
(out of sync) mcs)
3.) double check that there is no mcs still in your path ("which mcs"
should return nothing)
4.) double check that the contents of the runtime subdirectory is the
contents of the latest monolite or monocharge
5.) make (ignore any file not found errors)
6.) make install (again, ignore any file not found errors)
7.) make fullbuild

It seems that the instructions are optimized for a preexisting install
that is installed in the same place as the cvs version is being installed.
 This is not the case with a preexisting rpm install.  The above will make
sure that mono is wiped clean and installed fresh.


> If I run "make fullbuild" in mono I get:
>   Your mono runtime and corlib are out of sync.
>   Corlib is: mscorlib
> So I then try "make PROFILE="atomic" fullbuild" which I still gives me:
>   System.Security.Cryptography/HMACSHA1.cs(110) error CS0246:
>   Cannot find type `HMAC'
>   Compilation failed: 1 error(s), 0 warnings
>   make[1]: *** [../../class/lib/mscorlib.dll] Error 1
> Someone just doesn't want me running the latest version.  This seems
> overly complicated.  Thanks for all the help, any more suggestions?

More information about the Mono-devel-list mailing list