atom feed7 messages in org.freebsd.freebsd-gnomeMonodoc on FreeBSD: Success!
FromSent OnAttachments
Christopher NehrenAug 13, 2004 7:33 am 
Christopher NehrenAug 13, 2004 7:52 am 
Christopher NehrenAug 13, 2004 9:04 am 
Pav LucistnikAug 13, 2004 9:14 am 
Christopher NehrenAug 13, 2004 9:41 am 
Jeremy MessengerAug 13, 2004 10:37 am 
Christopher NehrenAug 13, 2004 10:59 am 
Subject:Monodoc on FreeBSD: Success!
From:Christopher Nehren (apei@comcast.net)
Date:Aug 13, 2004 7:33:59 am
List:org.freebsd.freebsd-gnome

I've just gotten Monodoc 1.0.0 to build and run [1] on FreeBSD, with a small (thread-related) patch[2]. This is cool not only because it marks one more .NET program that works on FreeBSD (and a nice one at that), but it opens the door for its dependencies, such as the illustrious MonoDevelop.

I couldn't get this to build until today, after I updated my -CURRENT. My theory is that there's been some changes in libpthread between when I first moved to -CURRENT and when I updated. I'll have a FreeBSD port ready sometime soon, and I'd appreciate it if people with different OSRELs would test this, see if it works, and tell me their OSREL and libmap.conf situation. For the record, my OSREL is 502128 and I have my libmap.conf set up to work with nVidia drivers with mono mapped as John Merryweather Cooper suggested in a previous post.

[1]: Proof: http://prophecy.dyndns.org/~apeiron/monodoc-on-freebsd.png Yes, I know, I use the gtk-bluecurve theme. RedHat does one thing well, and that's look nice :-).

[2]: See my previous message to this list, entitled "Mono core dumping if mcs is called with -pkg". The workaround is to call pkg-config in backticks, which is what my patch to Makefile.in does. When Mono / libpthread work nicely with one another, that patch will be obsoleted and thence removed. I'll also be investigating why this causes Mono to core dump.