Re: Mono is broken
On 2012/10/20 02:33, Nigel Taylor wrote: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. From what I remember on i386, - builds fail far more frequently under dpb than outside it - if it doesn't build outside dpb, then rebooting usually fixes this(!!!) Recently I have seen fewer problems building mono itself, but ports depending on it still often fail.
Re: Mono is broken
On 10/20/12 06:51, Amit Kulkarni wrote: On Fri, Oct 19, 2012 at 8:33 PM, Nigel Taylor njtay...@asterisk.demon.co.uk wrote: On 10/19/12 20:30, Amit Kulkarni wrote: On Mon, Aug 20, 2012 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. any movement on this guys? i am unable to build mono for last 5 days on amd64. i don't have /etc/malloc.conf defined. tried with or without ccache until it is fixed, i marked the kde 4.9.2 mono-related ports as broken in github. . The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. I did a userland/xenocara/release rebuild yesterday on amd64/i386, and have deleted older packages including mono on both i386/amd64, and leaving them rebuilding them with dpb overnight. I will know in about 10hr, if mono doesn't build. Could copy to where you can download from, if I get a build that works. please if somebody can upload it to the snapshots in the ftp mirrors. this is the only package which i can't build on amd64. thanks . On i386 build... I=1703 B=2 Q=5456 T=938 F=0 !=49 L=lang/gcc/4.6 E=lang/mono lang/gcc/4.6,-c++ gcc/4.6 takea priority holds more up from building, so haven't tried a continuation of the mono build yet. On amd64 build ... I=4197 B=10 Q=3284 T=564 F=0 !=107 L=devel/jdk/1.6 E= devel/jdk/1.6 devel/jdk/1.6 - looks to have hit a parallel build issue, mkdir when directory exists. Continued make from point of failure. There is change to devel/jdk/1.6 not included. $ ls -lrt mono* -rw-r--r-- 4 3666843 Oct 13 06:37 mono-gtk2-2.12.10p6.tgz -rw-r--r-- 4 3050255 Oct 13 13:59 monotone-0.39.tgz -rw-r--r-- 452420 Oct 13 16:13 mono-avahi-0.6.31p0.tgz -rw-r--r-- 4 7359268 Oct 13 16:17 monodevelop-2.4.2p2.tgz -rw-r--r-- 4 302299 Oct 15 18:38 mono-gnome-2.24.2p1.tgz -rw-r--r-- 3 69706946 Oct 20 04:53 mono-2.10.9p0.tgz -rw-r--r-- 3 485979 Oct 20 06:19 mono-addins-0.6.2.tgz -rw-r--r-- 3 251194 Oct 20 07:03 mono-gdata-1.9.0.0.tgz -rw-r--r-- 3 187492 Oct 20 07:05 mono-taglib-2.0.3.7p1.tgz -rw-r--r-- 396285 Oct 20 07:05 mono-zeroconf-0.9.0p3.tgz -rw-r--r-- 313547 Oct 20 07:06 mono-notify-0.4.0p2.tgz -rw-r--r-- 3 409137 Oct 20 09:18 mono-xsp-2.10.2p0.tgz -rw-r--r-- 3 1041450 Oct 20 09:26 mono-basic-2.10.tgz Mono built ok, with dpb on amd64. mono should be on the snapshots, it is for i386, not for amd64.
Re: Mono is broken
On 10/20/12 11:21, Stuart Henderson wrote: On 2012/10/20 02:33, Nigel Taylor wrote: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. From what I remember on i386, - builds fail far more frequently under dpb than outside it - if it doesn't build outside dpb, then rebooting usually fixes this(!!!) I usually reboot if I see top has changed from Swap 0K/4095M to xxxM/4095M, occurs quite often after a dpb run. i386 build failed here gmake[7]: Entering directory `/usr/ports/pobj/mono-2.10.9/mono-2.10.9/mcs/class/Microsoft.VisualC' MONO_PATH=./../../class/lib/basic:$MONO_PATH /usr/ports/pobj/mono-2.10.9/mono-2.10.9/runtime/mono-wrapper ./../../class/lib/basic/gacutil.exe /i ./../../class/lib/net_2_0/Microsoft.Visual C.dll /f /root /usr/ports/pobj/mono-2.10.9/fake-i386/usr/local/lib /package 2.0 Failure adding assembly ./../../class/lib/net_2_0/Microsoft.VisualC.dll to the cache: Strong name cannot be verified for delay-signed assembly Error while executing /usr/ports/pobj/mono-2.10.9/mono-2.10.9/mono/mini/mono --config /usr/ports/pobj/mono-2.10.9/mono-2.10.9/runtime/etc/mono/config ./../../class/lib/basic/gacutil.exe /i . /../../class/lib/net_2_0/Microsoft.VisualC.dll /f /root /usr/ports/pobj/mono-2.10.9/fake-i386/usr/local/lib /package 2.0 gmake[7]: *** [install-local] Error 2 $ pwd /usr/ports/pobj/mono-2.10.9/mono-2.10.9/mcs/class/Microsoft.VisualC $ ls -l total 18836 drwxr-xr-x 2 ntayl01 wsrc 512 Feb 3 2012 Assembly -rw-r--r-- 1 ntayl01 wsrc 194 Feb 3 2012 ChangeLog -rw-r--r-- 1 ntayl01 wsrc 200 Nov 15 2011 Makefile drwxr-xr-x 2 ntayl01 wsrc 512 Feb 3 2012 Microsoft.VisualC -rw-r--r-- 1 ntayl01 wsrc 510 Nov 15 2011 Microsoft.VisualC.dll.sources -rw--- 1 ntayl01 wsrc 9609916 Oct 20 04:32 mono.core Got suck here, on i386, couple of tries... I did a gmake clean in the directory, then continued with make package, then built, this was with dpb still running and so no reboot as yet. Recently I have seen fewer problems building mono itself, but ports depending on it still often fail. Amit, you can try my mono build for amd64 - https://www.asterisk.me.uk/amd64/mono-2.10.9p0.tgz Very slow adsl speeds, very poor ISP, line up and down. Must switch to a new ISP. These packages are available... $ lynx https://www.asterisk.me.uk/amd64/ Index of /amd64 NameLast modified Size Description _ [DIR] Parent Directory18-May-2012 22:38 - [ ] mono-2.10.9p0.tgz 20-Oct-2012 04:53 66.5M [ ] mono-addins-0.6.2.tgz 20-Oct-2012 06:19 475k [ ] mono-avahi-0.6.31p0.tgz 13-Oct-2012 16:1351k [ ] mono-basic-2.10.tgz 20-Oct-2012 09:26 1017k [ ] mono-gdata-1.9.0.0.tgz 20-Oct-2012 07:03 245k [ ] mono-gnome-2.24.2p1.tgz 15-Oct-2012 18:38 295k [ ] mono-gtk2-2.12.10p6.tgz 13-Oct-2012 06:37 3.5M [ ] mono-notify-0.4.0p2.tgz 20-Oct-2012 07:0613k [ ] mono-taglib-2.0.3.7p.. 20-Oct-2012 07:05 183k [ ] mono-xsp-2.10.2p0.tgz 20-Oct-2012 09:18 400k [ ] mono-zeroconf-0.9.0p.. 20-Oct-2012 07:0594k [ ] monodevelop-2.4.2p2.tgz 13-Oct-2012 16:17 7.0M [ ] monotone-0.39.tgz 13-Oct-2012 13:59 2.9M ___
Re: Mono is broken
On Sat, Oct 20, 2012 at 9:12 AM, Nigel Taylor njtay...@asterisk.demon.co.uk wrote: On 10/20/12 11:21, Stuart Henderson wrote: On 2012/10/20 02:33, Nigel Taylor wrote: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. From what I remember on i386, - builds fail far more frequently under dpb than outside it - if it doesn't build outside dpb, then rebooting usually fixes this(!!!) I usually reboot if I see top has changed from Swap 0K/4095M to xxxM/4095M, occurs quite often after a dpb run. i386 build failed here gmake[7]: Entering directory `/usr/ports/pobj/mono-2.10.9/mono-2.10.9/mcs/class/Microsoft.VisualC' MONO_PATH=./../../class/lib/basic:$MONO_PATH /usr/ports/pobj/mono-2.10.9/mono-2.10.9/runtime/mono-wrapper ./../../class/lib/basic/gacutil.exe /i ./../../class/lib/net_2_0/Microsoft.Visual C.dll /f /root /usr/ports/pobj/mono-2.10.9/fake-i386/usr/local/lib /package 2.0 Failure adding assembly ./../../class/lib/net_2_0/Microsoft.VisualC.dll to the cache: Strong name cannot be verified for delay-signed assembly Error while executing /usr/ports/pobj/mono-2.10.9/mono-2.10.9/mono/mini/mono --config /usr/ports/pobj/mono-2.10.9/mono-2.10.9/runtime/etc/mono/config ./../../class/lib/basic/gacutil.exe /i . /../../class/lib/net_2_0/Microsoft.VisualC.dll /f /root /usr/ports/pobj/mono-2.10.9/fake-i386/usr/local/lib /package 2.0 gmake[7]: *** [install-local] Error 2 $ pwd /usr/ports/pobj/mono-2.10.9/mono-2.10.9/mcs/class/Microsoft.VisualC $ ls -l total 18836 drwxr-xr-x 2 ntayl01 wsrc 512 Feb 3 2012 Assembly -rw-r--r-- 1 ntayl01 wsrc 194 Feb 3 2012 ChangeLog -rw-r--r-- 1 ntayl01 wsrc 200 Nov 15 2011 Makefile drwxr-xr-x 2 ntayl01 wsrc 512 Feb 3 2012 Microsoft.VisualC -rw-r--r-- 1 ntayl01 wsrc 510 Nov 15 2011 Microsoft.VisualC.dll.sources -rw--- 1 ntayl01 wsrc 9609916 Oct 20 04:32 mono.core Got suck here, on i386, couple of tries... I did a gmake clean in the directory, then continued with make package, then built, this was with dpb still running and so no reboot as yet. Recently I have seen fewer problems building mono itself, but ports depending on it still often fail. Amit, you can try my mono build for amd64 - https://www.asterisk.me.uk/amd64/mono-2.10.9p0.tgz Very slow adsl speeds, very poor ISP, line up and down. Must switch to a new ISP. These packages are available... $ lynx https://www.asterisk.me.uk/amd64/ Index of /amd64 NameLast modified Size Description _ [DIR] Parent Directory18-May-2012 22:38 - [ ] mono-2.10.9p0.tgz 20-Oct-2012 04:53 66.5M [ ] mono-addins-0.6.2.tgz 20-Oct-2012 06:19 475k [ ] mono-avahi-0.6.31p0.tgz 13-Oct-2012 16:1351k [ ] mono-basic-2.10.tgz 20-Oct-2012 09:26 1017k [ ] mono-gdata-1.9.0.0.tgz 20-Oct-2012 07:03 245k [ ] mono-gnome-2.24.2p1.tgz 15-Oct-2012 18:38 295k [ ] mono-gtk2-2.12.10p6.tgz 13-Oct-2012 06:37 3.5M [ ] mono-notify-0.4.0p2.tgz 20-Oct-2012 07:0613k [ ] mono-taglib-2.0.3.7p.. 20-Oct-2012 07:05 183k [ ] mono-xsp-2.10.2p0.tgz 20-Oct-2012 09:18 400k [ ] mono-zeroconf-0.9.0p.. 20-Oct-2012 07:0594k [ ] monodevelop-2.4.2p2.tgz 13-Oct-2012 16:17 7.0M [ ] monotone-0.39.tgz 13-Oct-2012 13:59 2.9M ___ thanks nigel, appreciate that a lot.
Re: Mono is broken
Nigel Taylor: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. Right. Mono has a certain probability of building, i.e., sometimes it builds and sometimes it doesn't. THIS IS NOT ACCEPTABLE. Previously, when producing amd64 snapshots, I restarted the mono build as often as necessary to get it built, but I have stopped doing that. Sometimes mono packages will show up in a snapshot, but mostly they won't. Mono is broken. If people need it, they better fix it. Retrying builds until one succeeds does not constitute a fix. Build environment voodoo (dpb, no dpb, reboot before building) does not constitute a fix. -- Christian naddy Weisgerber na...@mips.inka.de
Re: Mono is broken
On Sat, Oct 20, 2012 at 05:03:22PM +0200, Christian Weisgerber wrote: Nigel Taylor: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. Right. Mono has a certain probability of building, i.e., sometimes it builds and sometimes it doesn't. THIS IS NOT ACCEPTABLE. Previously, when producing amd64 snapshots, I restarted the mono build as often as necessary to get it built, but I have stopped doing that. Sometimes mono packages will show up in a snapshot, but mostly they won't. Mono is broken. If people need it, they better fix it. Retrying builds until one succeeds does not constitute a fix. Build environment voodoo (dpb, no dpb, reboot before building) does not constitute a fix. I'm sure the reliability of mono builds has NOTHING to do with not using dpb, and a lot to do with not doing anything significant on the same machine concurrently. There is a race condition in that build process. It tends not to hit it if you're not doing anything else at all on the same machine at the same time.
Re: Mono is broken
On 10/20/12 16:03, Christian Weisgerber wrote: Nigel Taylor: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. Right. Mono has a certain probability of building, i.e., sometimes it builds and sometimes it doesn't. THIS IS NOT ACCEPTABLE. Previously, when producing amd64 snapshots, I restarted the mono build as often as necessary to get it built, but I have stopped doing that. Sometimes mono packages will show up in a snapshot, but mostly they won't. Mono is broken. If people need it, they better fix it. Retrying builds until one succeeds does not constitute a fix. Build environment voodoo (dpb, no dpb, reboot before building) does not constitute a fix. I have no interest in mono, I don't install mono on my machines, only build it because it's there. If it was marked as BROKEN, I wouldn't be trying to build it, and wouldn't miss it.
Re: Mono is broken
Marc Espie wrote: On Sat, Oct 20, 2012 at 05:03:22PM +0200, Christian Weisgerber wrote: Nigel Taylor: The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. Right. Mono has a certain probability of building, i.e., sometimes it builds and sometimes it doesn't. THIS IS NOT ACCEPTABLE. Previously, when producing amd64 snapshots, I restarted the mono build as often as necessary to get it built, but I have stopped doing that. Sometimes mono packages will show up in a snapshot, but mostly they won't. Mono is broken. If people need it, they better fix it. Retrying builds until one succeeds does not constitute a fix. Build environment voodoo (dpb, no dpb, reboot before building) does not constitute a fix. I'm sure the reliability of mono builds has NOTHING to do with not using dpb, and a lot to do with not doing anything significant on the same machine concurrently. There is a race condition in that build process. It tends not to hit it if you're not doing anything else at all on the same machine at the same time. I'm not using mono, but brief look at FreeBSD port shows at least one threads related patch which is not in our port. http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/mono/files/patch-mono_metadata_appdomain.c https://bugzilla.novell.com/show_bug.cgi?id=528830 Not sure about mono build process, but if mono builds its parts by itself, threading issues may impact on this. Alexey
Re: Mono is broken
On Mon, Aug 20, 2012 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. any movement on this guys? i am unable to build mono for last 5 days on amd64. i don't have /etc/malloc.conf defined. tried with or without ccache until it is fixed, i marked the kde 4.9.2 mono-related ports as broken in github.
Re: Mono is broken
On Fri, Oct 19, 2012 at 02:30:59PM -0500, Amit Kulkarni wrote: On Mon, Aug 20, 2012 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. any movement on this guys? i am unable to build mono for last 5 days on amd64. i don't have /etc/malloc.conf defined. tried with or without ccache I personnally never, _ever_ had any issue in building mono on amd64. But I don't run dpb(1) on this arch. As a matter of fact I compiled mono yesterday just fine... until it is fixed, i marked the kde 4.9.2 mono-related ports as broken in github. -- Antoine
Re: Mono is broken
On 10/19/12 20:30, Amit Kulkarni wrote: On Mon, Aug 20, 2012 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. any movement on this guys? i am unable to build mono for last 5 days on amd64. i don't have /etc/malloc.conf defined. tried with or without ccache until it is fixed, i marked the kde 4.9.2 mono-related ports as broken in github. . The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. I did a userland/xenocara/release rebuild yesterday on amd64/i386, and have deleted older packages including mono on both i386/amd64, and leaving them rebuilding them with dpb overnight. I will know in about 10hr, if mono doesn't build. Could copy to where you can download from, if I get a build that works.
Re: Mono is broken
On Fri, Oct 19, 2012 at 8:33 PM, Nigel Taylor njtay...@asterisk.demon.co.uk wrote: On 10/19/12 20:30, Amit Kulkarni wrote: On Mon, Aug 20, 2012 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. any movement on this guys? i am unable to build mono for last 5 days on amd64. i don't have /etc/malloc.conf defined. tried with or without ccache until it is fixed, i marked the kde 4.9.2 mono-related ports as broken in github. . The last mono I built was 8 Oct on amd64, 9 Oct on i386, didn't work first time as I recall on amd64, that was using dpb. When I hit a failure, I just use make, once I have finished with the dpb building, which continues from the point of failure, I may have rebooted before running the make. Never hit a mono recently where I couldn't build it, after one or more retries. I did a userland/xenocara/release rebuild yesterday on amd64/i386, and have deleted older packages including mono on both i386/amd64, and leaving them rebuilding them with dpb overnight. I will know in about 10hr, if mono doesn't build. Could copy to where you can download from, if I get a build that works. please if somebody can upload it to the snapshots in the ftp mirrors. this is the only package which i can't build on amd64. thanks
Re: Mono is broken
On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. That is why you have a no_mono FLAVOR. The mono bits are _not_ needed. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp. I'd rather see the core of the mono build issue fixed. -- Antoine
Re: Mono is broken
On Mon, Aug 20, 2012 at 01:12:55AM +0100, Nigel Taylor wrote: My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. Beagle is dead. The developers confirmed the dead of the project long time ago. -- Juan Francisco Cantero Hurtado http://juanfra.info
Mono is broken
Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. -- Christian naddy Weisgerber na...@mips.inka.de
Re: Mono is broken
On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? -- Antoine
Re: Mono is broken
Hi, On Sun, Aug 19, 2012 at 3:22 PM, Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? I haven't had much trouble building nant or boo on i386. I got a report a few weeks ago regarding issues with building nant on amd64, which sounded like the old issues it use to have. I forwarded the email to ports@ suggesting that it be marked as broken again on amd64 and asking for additional guidance/feedback but I didn't receive any responses. Thanks, Ryan -- Antoine
Re: Mono is broken
On 08/19/12 23:22, Antoine Jacoutot wrote: On Sun, Aug 19, 2012 at 09:50:59PM +0200, Christian Weisgerber wrote: Mono is broken. On amd64, lang/mono itself sometimes crashes during the build. (It's completely unbuildable with MALLOC_OPTIONS=S.) Sometimes, x11/mono-gtk2 crashes. devel/nant frequently gets stuck. lang/boo frequently gets stuck. Seen all these fail on occasion when building here. I'm tired of manually retrying builds until this crap finally packages. Does anybody actually use mono-based packages? Do they even run? sthen@ is also struggling to get mono built on i386. I built mono for i386 on Aug 18 for libpthread.so.17.0. I have seen mono fail to build on i386 in the past, and more often than on amd64. Somebody needs to step up and fix mono, or I'm going to push for marking all of this stuff as BROKEN and ripping its tentacles out of Gnome. GNOME does not care; it does not depend on mono. FWIW yes I do use mono based apps daily and it works fine for me (but I use pkg, I never build from ports). Did you talk to maintainer ? Building gnome does require mono, mail/gmime has a build dependency on mono to build gmime-sharp. I took the mono dependency out of mail/gmime, so it no longer builds gmime-sharp just gmime. A change I made back when mono was failing because of the switch to rthreads. It allowed me to build gnome while mono wasn't building. My searches found one project using gmime-sharp, Beagle which has not been ported to OpenBSD. The project looks dead, it was on gnome svn, but 2-3 years since it's been updated. The Beagle project web site was down. I couldn't find a single port that uses gmime-sharp. gmime-sharp is redundant. I can supply a diff for mail/gmime without gmime-sharp.
