Beta 2 of the mono development system is available. Perhaps this will reduce the other bugs showing up under mono... Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: It would also be nice to have an ebuild that needed all the parts for a complete development system.
believe me, we're well aware it's out. I've got most of the updated ebuilds ready, expect updates today or tomorrow. As for a "meta-ebuild", what advantage do you see in this? If you are installing an app that uses gtk-sharp, etc, the deps will get pulled in. If you are developing stuff, i think you should be able to know you have to install various components. I'm not completely opposed to it, but I need some convincing of it's value before I'd consider it.
We aim to please. beta2 is in ~x86 and a few pieces are ~amd64. Test away. that's what beta2s are for. (:
Nice work Peter!
Hmm, I think I was a bit too quick... mono, gtk-sharp, gtksourceview-sharp and gecko-sharp all compiled nicely. But when I try to compile monodoc or monodevelop I get this: Making all in class make[1]: Entering directory `/var/tmp/portage/monodoc-0.16/work/monodoc-0.16/cla ss' mono --debug ../browser/assembler.exe --ecmaspec ./../ecma334 -o ecma334 ** (../browser/assembler.exe:13550): WARNING **: Could not find assembly ICSharp Code.SharpZipLib, references from /usr/lib/mono/gac/monodoc/1.0.0.0__0738eb9f132 ed756/monodoc.dll (assemblyref_index=3) Major/Minor: 0,31 Build: 0,0 Token: 1b03e6acf1164f73 Unhandled Exception: System.NullReferenceException: A null value was found where an object instance was required. Caught signal 2 make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs.... make[1]: *** wait: No child processes. Stop. make: *** [all-recursive] Error 1 and this: mcs -debug -out:browser.exe ./browser.cs ./list.cs ./elabel.cs ./history.cs ./Contributions.cs ./XmlNodeWriter.cs -resource:./../monodoc.png,monodoc.png -resource:./browser.glade,browser.glade -pkg:gtkhtml-sharp -pkg:glade-sharp -r:System.Web.Services -r:./monodoc.dll Compilation succeeded mcs /debug /out:assembler.exe ./assembler.cs -r:ICSharpCode.SharpZipLib.dll -r:./monodoc.dll Compilation succeeded mcs ./normalize.cs -out:normalize.exe Compilation succeeded mcs ./mod.cs -r:./monodoc.dll -out:mod.exe Compilation succeeded make[1]: Leaving directory `/var/tmp/portage/monodoc-0.16/work/monodoc-0.16/browser' Making all in class make[1]: Entering directory `/var/tmp/portage/monodoc-0.16/work/monodoc-0.16/class' mono --debug ../browser/assembler.exe --ecmaspec ./../ecma334 -o ecma334 ** (../browser/assembler.exe:14379): WARNING **: Could not find assembly ICSharpCode.SharpZipLib, references from /usr/lib/mono/gac/monodoc/1.0.0.0__0738eb9f132ed756/monodoc.dll (assemblyref_index=3) Major/Minor: 0,31 Build: 0,0 Token: 1b03e6acf1164f73 Unhandled Exception: System.NullReferenceException: A null value was found where an object instance was required.
BTW, this is what I have: tux /usr/lib/mono$ find . | grep ICSharpCode.SharpZipLib.dll ./1.0/ICSharpCode.SharpZipLib.dll ./gac/ICSharpCode.SharpZipLib/0.6.0.0__1b03e6acf1164f73/ICSharpCode.SharpZipLib.dll
And that dll belongs to mono: tux ~$ qpkg -f /usr/lib/mono/1.0/ICSharpCode.SharpZipLib.dll dev-dotnet/mono * tux ~$ emerge -p mono These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-dotnet/mono-0.95
I thought i'd added a good warning to that ebuild as well. Can you please unmerge monodoc, then re-emerge it again. i'm 95% this is the usual problem with old dll's lying around creating issues for the upgrade.
Yep, that was it. Thanks Peter.
You guys are fast. It doesn't go all the way through for me. I think I've uninstalled everything so it should build cleanly. (error at bottom). The case for the meta builds is I'm being lazy. The problem with doing an emerge mono is that I don't know all the packages that can go with it, and I'd rather just emerge allmono and have everything at my disposal. I suffer from do it myself syndrome and to counteract it I try to make it really obvious that it's been done by someone else before. Also if it's on my hard disk I will know that all packages have been successfully installed, and are all at the appropriete version. (beta2 in this case). when emerging mono it get's this far and then just stops. I can only break out. MONO_PATH=. ../../mono/mini/mono --config ../../data/config ./../gacutil.exe /i ./nunit.util.dll /f /package 1.0 /root /var/tmp/portage/mono-0.95/image//usr/lib Package exported to: /var/tmp/portage/mono-0.95/image//usr/lib/mono/1.0 nunit.util installed into the gac (/var/tmp/portage/mono-0.95/image//usr/lib/mono/gac/)
@Chris: Can you please open a new seperate bug for that issue? On it can you post a bit more of the text before it stops there? I'm going to wager that this is the first file it's trying to install into the GAC. We've seen reports like this if the runtime is not working, as the gacutil install is the first time the built runtime gets used. Can you also post the output from "emerge info" for us?
I opened a new bug for my problem. (#53111)
