Date: Mon, 13 Nov 2006 18:02:50 -0700 From: Lorin Lund <wbs@infowest.com> To: cremes.devlist@mac.com Cc: freebsd-questions@freebsd.org Subject: Re: MAC OS X connection to FreeBSD? Message-ID: <455915BA.9090300@infowest.com> In-Reply-To: <62104DC1-8AD2-41E1-B469-51CAC91A8D8B@mac.com> References: <454E9F7B.5010105@outstep.com> <454EB6D6.3030807@infowest.com> <454EBEEC.1060002@u.washington.edu> <454F210C.9000602@outstep.com> <004001c70706$0d571ec0$3c01a8c0@coolf89ea26645> <62104DC1-8AD2-41E1-B469-51CAC91A8D8B@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> The biggest problem with MacOS X is that a lot of UNIX software that >> runs on FreeBSD and such, is not ported to MacOSX, and it's very >> difficult to compile on MacOSX. > > This is completely wrong. Take a look at macports [1] (formerly > darwinports) for a large repository of UNIX software that compiles > very cleanly on OSX. It's nearly 7 years since OSX shipped to the > public. In that time, most opensource software was updated to compile > cleanly on OSX. The primary changes to allow this were to the > "configure" scripts so they recognize darwin as a base OS. If other > patches were necessary, most software maintainers accepted these > patches back into their trunk. > > OSX has excellent support for most UNIX software. > > cr > > [1] macports.org In trying to compile A+ (see aplusdev.org) I had a few problems getting it compiled for FreeBSD (Because the A+ code was using the wrong macro to identify FreeBSD) But my efforts to compile the latest version for OS X.3 PPC have brought out errors that look like compiler errors. In my view porting to the MAC is harder (though I very much wish it weren't)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?455915BA.9090300>