Date: Mon, 9 Dec 1996 14:57:20 +0100 (MEZ) From: "Hr.Ladavac" <lada@ws2301.gud.siemens.co.at> To: tjb@fnbc.com Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD porting -- distinguishing CPP definition? Message-ID: <199612091357.AA216649840@ws2301.gud.siemens.co.at> In-Reply-To: <4306.9612091208@lia33.fnbc.co.uk> from "Tim Bissell" at Dec 9, 96 12:08:11 pm
next in thread | previous in thread | raw e-mail | index | archive | help
E-mail message from Tim Bissell contained: > > Chris Csanady replied: > > >You may want to take a look at section 4.2.6 of the freebsd handbook. There > >are also some notes in there which you might find useful, even if you are > >not specifically producing something for the ports collection. > > Typical. My first mail to questions NOT to be eaten en-route, and with an > embarassingly RTFM-like answer! Thanks, Chris. Still, I guess it means > anyone looking for information about GNUstep in the mail archives will get > routed to me... > > I'm off to a more appropriate mailing list ... errr, anyone know which one > it would be? GNUstep is (or will be) a language (objective-C) some class > and GUI libraries and some programs, conforming to the OPENSTEP standard. > > I'm interested in a technical mailing list discussing problems with porting > software to FreeBSD (e.g. availability of threads libraries, dynamic loading > etc.) None of the lists described in handbook292 really fit; freebsd-ports > seems closest. Threads: pthread API is supported natively in -current (and perhaps 2.2) Available as a port/package as well. Dynloading: SunOS "standard" family of dlopen(3), dlsym(3) ... /Marino > > Thanks again, > > Tim >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612091357.AA216649840>