From owner-freebsd-gnome@FreeBSD.ORG Fri Aug 13 14:34:20 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36D9C16A4CE for ; Fri, 13 Aug 2004 14:34:20 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6AB743D4C for ; Fri, 13 Aug 2004 14:34:19 +0000 (GMT) (envelope-from apeiron@comcast.net) Received: from prophecy.velum (pcp08490587pcs.levtwn01.pa.comcast.net[68.83.169.224]) by comcast.net (sccrmhc11) with SMTP id <20040813143419011004ofe6e> (Authid: apeiron@comcast.net); Fri, 13 Aug 2004 14:34:19 +0000 Date: Fri, 13 Aug 2004 10:34:17 -0400 From: Christopher Nehren To: FreeBSD GNOME List Message-ID: <20040813143417.GA51926@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline X-Please-CC-Me: In List And Group Replies User-Agent: Mutt/1.5.6i Subject: Monodoc on FreeBSD: Success! X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 14:34:20 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've just gotten Monodoc 1.0.0 to build and run [1] on FreeBSD, with a smal= l=20 (thread-related) patch[2]. This is cool not only because it marks one more = =2ENET=20 program that works on FreeBSD (and a nice one at that), but it opens the do= or=20 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 m= cs=20 is called with -pkg". The workaround is to call pkg-config in backticks, wh= ich=20 is what my patch to Makefile.in does. When Mono / libpthread work nicely wi= th=20 one another, that patch will be obsoleted and thence removed. I'll also be= =20 investigating why this causes Mono to core dump. --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBHNFpk/lo7zvzJioRAsPkAJ4wYIkhk3mrMwC+MstUccxX54S/mwCeIJWt sUh2WKKl5GFG5wV+EFwzVSc= =M1y2 -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--