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-- 4 52420 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-- 3 96285 Oct 20 07:05 mono-zeroconf-0.9.0p3.tgz -rw-r--r-- 3 13547 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.
