Date: Sun, 21 Dec 2003 19:12:36 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: John Merryweather Cooper <johnmary@adelphia.net> Cc: Stephen@IPCoast.com Subject: Re: FW: Is mono 0.29 on FreeBSD 5.1 / 4.9 working for you? Message-ID: <1072051956.56655.49.camel@shumai.marcuscom.com> In-Reply-To: <3FE48678.2040006@adelphia.net> References: <000301c3c71c$7f4d2600$0300a8c0@DOVY2> <3FE48678.2040006@adelphia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-XegoExC4pHbSJT9305KM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2003-12-20 at 12:27, John Merryweather Cooper wrote: > I'm throwing freebsd-gnome and Joe on because this is of wide interest: >=20 > My primary interest in lang/mono is getting the latest version of=20 > comms/gfax to work (I'm the maintainer). gfax doesn't use sockets (and=20 > it won't compile with the current versions of lang/mono and=20 > x11-toolkits/gtk-sharp), so I'm waiting for the gfax Beta to catch up. >=20 > I think part of the problem is that mono is using a "lite" version of=20 > the mcs compiler (without the C# runtime included in mcs). I think the=20 > "lite" version makes certain assumptions about the platform it's on that=20 > are prejudicial to FreeBSD. :) However, porting mcs is proving a=20 > little difficult because: 1) the full mcs compiler is not self-hosting=20 > (you need a special boot-up mcs to build) 2) the configuration scripts=20 > seem to be a tad linux-centric. >=20 > I believe if we can get a working port for lang/mcs, that we'll be able=20 > to fix problems like sockets at the C# runtime level. I believe trying=20 > to fix these at the mono runtime level will be frustrating. >=20 > But, your mileage may vary . . . >=20 > Yes, I would like playing with anything that builds using mono: it will=20 > make the learning curve less steep when the general release version of=20 > gfax hits. My hope is the new OS X/FreeBSD mono project will get off the ground, and the issues with boehm-gc threading on FreeBSD will be addressed.=20 Once that is resolved, Mono porting on FreeBSD should become much easier. In the meantime, if people are into fixing what other bugs may exist with mono on FreeBSD, I urge you to configure mono without garbage collection. Yes, it will be a pig, but it should eliminate some low-level problems and allow one to focus on other runtime and compile time issues. Joe >=20 > jmc >=20 > Mary A. Cooper wrote: >=20 > >=20 > > -----Original Message----- > > From: Stephen Gutknecht (IPCoast) [mailto:Stephen@IPCoast.com]=20 > > Sent: Saturday, December 20, 2003 7:44 AM > > To: johnmary@adelphia.net > > Subject: Is mono 0.29 on FreeBSD 5.1 / 4.9 working for you? > >=20 > >=20 > > Hi John, > >=20 > > I saw you had some recently activity with Mono on FreeBSD. > >=20 > > I wanted to see if you had any luck getting network socket applications= to > > work? We tried jabber-net and it will not work on FreeBSD but works f= ine > > with Mono on Linux and Win32. > >=20 > > We believe that the FreeBSD socket interfaces are not correctly mating = with > > Mono. > >=20 > > We can give you instructions on how to compile / try jabber-net on Mono= if > > you would like to help troubleshoot. > >=20 > > Thank you. > >=20 > > Stephen Gutknecht > >=20 >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-XegoExC4pHbSJT9305KM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/5jb0b2iPiv4Uz4cRAjGbAJ461R2hS8y3ExvkGnkd5+Kx20P9PwCgr6hh 9QABVtRSZOMeOYhmrQc13Wc= =rIK9 -----END PGP SIGNATURE----- --=-XegoExC4pHbSJT9305KM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1072051956.56655.49.camel>