Summary: | mono-0.28 freezes during compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jan Callewaert <jan.callewaert> |
Component: | [OLD] Development | Assignee: | dotnet project <dotnet> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jan Callewaert
2003-11-20 12:19:15 UTC
I have gotten 0.29 to compile in an ebuild: http://bugs.gentoo.org/show_bug.cgi?id=35077 Hopefully this will be added into portage soon. Have you run a recent memtest on this system? Have you run a recent memtest on this system? How do you do that? The funny thing is, i got it once compiled, but then i couldn't compile monodoc. Now i can't compile mono no more. This might end up being over aggressive CFLAGS, try changing down to something lower, like -O2 and -march=i686, if this works, I will start stripping flags on the mono build. with the optimization flag -O2 -mcpu=pentium4, the compilation stops at a different stage: touch ../../build/deps/Mono.PEToolkit.dll.stamp MONO_PATH="../../class/lib:$MONO_PATH" /var/tmp/portage/mono-0.28/work/mono-0.28/mono/mini/mono ../../mcs/mcs.exe -d:NET_1_1 -g /noconfig /unsafe /r:corlib.dll /r:System.Xml.dll /target:library /out:../../class/lib/Mono.PEToolkit.dll @Mono.PEToolkit.dll.sources lt-mono: mini-x86.c:3119: mono_arch_patch_code: Assertie `0' faalde. make[2]: *** [../../class/lib/Mono.PEToolkit.dll] Gedood make[2]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class/Mono.PEToolkit' make[1]: *** [all-recursive] Fout 1 make[1]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class' make: *** [all-recursive] Fout 1 !!! ERROR: dev-dotnet/mono-0.28 failed. !!! Function src_compile, Line 49, Exitcode 2 !!! MCS compilation failure -O2 -march=pentium4 crashes at: touch ../../build/deps/Mono.Data.TdsClient.dll.stamp MONO_PATH="../../class/lib:$MONO_PATH" /var/tmp/portage/mono-0.28/work/mono-0.28/mono/mini/mono ../../mcs/mcs.exe -d:NET_1_1 -g /noconfig /r:corlib.dll /r:System.dll /r:System.Xml.dll /r:System.EnterpriseServices.dll /r:System.Data.dll /r:Mono.Data.Tds.dll /target:library /out:../../class/lib/Mono.Data.TdsClient.dll @Mono.Data.TdsClient.dll.sources Compilation succeeded lt-mono: mini-x86.c:3119: mono_arch_patch_code: Assertie `0' faalde. make[2]: *** [../../class/lib/Mono.Data.TdsClient.dll] Afgebroken (geheugendump) make[2]: *** Bestand `../../class/lib/Mono.Data.TdsClient.dll' wordt verwijderd make[2]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class/Mono.Data.TdsClient' make[1]: *** [all-recursive] Fout 1 make[1]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class' make: *** [all-recursive] Fout 1 !!! ERROR: dev-dotnet/mono-0.28 failed. !!! Function src_compile, Line 49, Exitcode 2 !!! MCS compilation failure Even without any CFlAGS it fails to compile: touch ../../build/deps/ICSharpCode.SharpZipLib.dll.stamp MONO_PATH="../../class/lib:$MONO_PATH" /var/tmp/portage/mono-0.28/work/mono-0.28/mono/mini/mono ../../mcs/mcs.exe -d:NET_1_1 -g /noconfig /r:corlib.dll /r:System.dll /r:System.Xml.dll /target:library /out:../../class/lib/ICSharpCode.SharpZipLib.dll @ICSharpCode.SharpZipLib.dll.sources Compilation succeeded make[2]: *** [../../class/lib/ICSharpCode.SharpZipLib.dll] Gedood make[2]: *** Bestand `../../class/lib/ICSharpCode.SharpZipLib.dll' wordt verwijderd make[2]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class/ICSharpCode.SharpZipLib' make[1]: *** [all-recursive] Fout 1 make[1]: Leaving directory `/var/tmp/portage/mono-0.28/work/mcs-0.28/class' make: *** [all-recursive] Fout 1 !!! ERROR: dev-dotnet/mono-0.28 failed. !!! Function src_compile, Line 49, Exitcode 2 !!! MCS compilation failure So i don't think it has something to do with optimization flags. Maybe i need to mention that i'm using now kernel 2.6.0 test 11. Ah, im not sure if mono builds on 2.6, let me ask people in the know and get back to you. Is there anyway you can drop down to a 2.4 just to test this compile? The face that this keeps dying in random places is someone strange, and doing a memtest86 on your box might not be a bad idea. emerge -s memtest for more info. mono will build on 2.6 without an issue, so thats not the problem. That's not what i experience. It compiles with kernel 2.4.20 with agressive optimization flags, both mono and monodoc. But i see that i have filed the bug under test 9, now i am running test 11, maybe it does run under test 10? If you want to, i can compile that one again. i forgot to mention it, memtest doesn't give any errors. |