Mono 2.0 got released today. Reproducible: Always
As nobody seems to care anyway, I'll just mention, that everything that I've wrote in bug 220337 still holds, with following additions: 1. upstream '#ifdef 0' the part that ARG_MAX patch fixed; the note is that it doesn't work on slaware 11, any chances that cause they don't hahe this patch ? 2. upstream decided to use abomination called DOLT; on reasons I call it such: read the discussion in libtool archives Other than that, old ebuild with minimal modifications seems to work (well, at least it build).
would you mind sharing that adapted ebuild, i'd like to give it a shot
Created attachment 169172 [details] dev-lang/mono/mono-2.0.ebuild Simple copy of 1.9.1 did worked (with a few changes).
No: MONO_PATH="../../class/lib/net_1_1_bootstrap:$MONO_PATH" /var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/runtime/mono-wrapper ../../class/lib/net_1_1_bootstrap/sn.exe -q -R ../../class/lib/default/Mono.Data.SqliteClient.dll ../../class/mono.snk Assembly ../../class/lib/default/Mono.Data.SqliteClient.dll signed. ** ERROR:../../mono/io-layer/handles-private.h:160:_wapi_handle_set_signal_state: assertion failed: (thr_ret == 0) make[8]: *** [../../class/lib/default/Mono.Data.SqliteClient.dll] Aborted make[8]: *** Deleting file `../../class/lib/default/Mono.Data.SqliteClient.dll' make[8]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs/class/Mono.Data.SqliteClient' make[7]: *** [do-all] Error 2 make[7]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs/class/Mono.Data.SqliteClient' make[6]: *** [all-recursive] Error 1 make[6]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs/class' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs' make[4]: *** [profile-do--default--all] Error 2 make[4]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs' make[3]: *** [profiles-do--all] Error 2 make[3]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/mcs' make[2]: *** [all-local] Error 2 make[2]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0/runtime' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/dev-lang/mono-2.0/work/mono-2.0' make: *** [all] Error 2 * If you are using any hardening features such as * PIE+SSP/SELinux/grsec/PAX then most probably this is the reason * why build has failed. In this case turn any active security * enhancements off and try emerging the package again * * ERROR: dev-lang/mono-2.0 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2944: Called die * The specific snippet of code: * die; * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-lang/mono-2.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/mono-2.0/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/' *
About ebuild: if I continue by (cd /.../ && sudo -u portage make ... && sudo -u portage /.../.compiled) all works fine. What's wrong with it anyway?
Created attachment 169240 [details] dev-util/mono-debugger-2.0.ebuild After installation of mono mono-tools & mono-debugger works (at least compiles).
Created attachment 169242 [details] dev-util/monodoc-2.0.ebuild
Created attachment 169244 [details] dev-util/mono-tools-2.0.ebuild
Created attachment 169250 [details] updated mono-tools ebuild, with patch from portage applied
Created attachment 169252 [details] updated patch for mono-tools
A bugfix release 2.0.1 came out today (only mono got updated, other related packages stayed at 2.0).
libgdiplus-2.0 (renamed 1.9 ebuild from portage) and mono-2.0.1 (renamed 2.0 from here) WFM on x86
(In reply to comment #12) > libgdiplus-2.0 (renamed 1.9 ebuild from portage) and mono-2.0.1 (renamed 2.0 > from here) WFM on x86 > WFM == Wait for masking?
WFM probably means Works For Me in this instance...
(In reply to comment #14) > WFM probably means Works For Me in this instance... > Good it is working. Pity it is not in portage.
Perhaps the dotnet herd needs some help, they aren't too active lately (i.e. no bugzilla traffic in last 2 months, cvs statistics are currently down). http://bugs.gentoo.org/custom_userhistory.cgi?matchstr=compnerd@gentoo.org http://bugs.gentoo.org/custom_userhistory.cgi?matchstr=jurek@gentoo.org http://www.gentoo.org/proj/en/devrel/undertakers/index.xml Jurek Bartuszek is finishing his thesis ( https://bugs.gentoo.org/show_bug.cgi?id=149480 ) Saleem Abdulrasool recruitement bug: https://bugs.gentoo.org/show_bug.cgi?id=71985 (according to google cache http://209.85.135.104/search?q=cache:lXfefPrx7lYJ:cia.vc/stats/author/compnerd+http://cia.vc/stats/author/compnerd/&hl=en&strip=1 he is active, only not in regards to dotnet herd).
Created attachment 171092 [details, diff] mono-fix-wsdl-troubles-with-muine.patch This patch for mono-2.0.1 fixes media-sound/muine build. https://bugzilla.novell.com/show_bug.cgi?id=434892
Masked in tree now. We're waiting for the full range of packages to get in before we unmask.
