Today mono released a new stable version, 1.9 Reproducible: Always
Created attachment 146696 [details] mono 1.9 (2.0 beta) ebuilds The archive contains overlays for the following packages: + www-apache/mod_mono-1.9 + dev-dotnet/xsp-1.9 + dev-dotnet/libgdiplus-1.9 + dev-dotnet/mono-addins-0.3.1 + dev-lang/mono-1.9 + dev-util/mono-tools-1.9 + dev-util/monodoc-1.9 Working for me on x86.
(In reply to comment #0) > Today mono released a new stable version, 1.9 > > Reproducible: Always > (In reply to comment #1) > Created an attachment (id=146696) [edit] > mono 1.9 (2.0 beta) ebuilds > > The archive contains overlays for the following packages: > > + www-apache/mod_mono-1.9 > + dev-dotnet/xsp-1.9 > + dev-dotnet/libgdiplus-1.9 > + dev-dotnet/mono-addins-0.3.1 > + dev-lang/mono-1.9 > + dev-util/mono-tools-1.9 > + dev-util/monodoc-1.9 > > Working for me on x86. > Thank you so much. Verified the mono build on amd65
Works for me on x86.
Created attachment 150515 [details, diff] mono-1.9-r1-ebuild.patch Use this patch to create a new "mono-1.9-r1.ebuild" file that includes a "moonlight" use flag. (Shortly said, I added a moonlight use flag.)
Created attachment 150669 [details] mono 1.9.1 (2.0 beta) ebuilds Mono 1.9.1 came out yesterday as a minor bugfix release. The archive contains overlays for the following packages: + dev-dotnet/xsp-1.9.1 + dev-lang/mono-1.9.1 Just combine it with the mono-1.9.tar.bz2 from above.
I'm not too familiar with mono's build process, but it seems that the moonlight USE doesn't seem to add the expected features, such as the 'mopen' command as described here ( http://tirania.org/blog/archive/2008/Apr-17.html ). smcs's paths seem to broken as well, I get this: $ smcs The assembly mscorlib.dll was not found or could not be loaded. It should have been installed in the `/usr/lib64/mono/2.1/mscorlib.dll' directory. :)
The moonlight use flag just provides the directory /usr/lib/mono/2.1 with the modified mscorlib.dll, System.Core.dll, smcs.exe and others. I've read the article about mopen and I couldn't find it in mono-1.9 or mono-tools-1.9. It seems as if it is currently only available in svn trunk/moon/. The Moonlight/2.1 API is even considered as "pre-alpha". smcs.exe works for me calling it without arguments. I couldn't find any example at first glance but it seems to me as if your problem origins from your x86_64 system?! I am going to have a deeper look at it later.
*** Bug 219000 has been marked as a duplicate of this bug. ***
I've updated the the ebuild for 1.9.1 to support hardened sources, would you like me to post it here?
Just post it if you want to. The only workaround I currently know for getting mono to work on a hardened system is running some sort of script that calls paxctl in the background. So I'm quite interested :)
Created attachment 153083 [details] ebuild with hardened checking and notifications the version of the ebuild I had built without even realizing there was one is so close to the one originally posted, didn't know if people would want the addition for checking for hardened sources. The added hardened flag support will check for the pax.softmode sysctl flag, which appears to be the only way to get mono to build on a grsec/pax kernel. Checks for the flag in the kernel config, then checks to see if it's active or not. Error message displayed states something more informative then "false not found" or of the like.
Fixed in CVS, thanks for your support! Rob, could you please file a new bug regarding the pax.softmode issue with a patch (against newest ebuild) attached? Thanks!
Could you please look at bug 220337, cause it affects mono 1.9.1, too ?
