Date: Fri, 29 Oct 1999 22:46:46 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: chris@calldei.com Cc: Randell Jesup <rjesup@wgate.com>, freebsd-arch@freebsd.org Subject: Re: liblinuxcompat (was Re: stpcpy()) Message-ID: <6365.941230006@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 29 Oct 1999 15:20:49 CDT." <19991029152049.F535@holly.calldei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <19991029152049.F535@holly.calldei.com>, Chris Costello writes: >On Fri, Oct 29, 1999, Poul-Henning Kamp wrote: >> > The bigger issue of Linux compatibility is essentially what >> >this is leading into. Currently the biggest users of stpcpy are >> >Linux applications. Frankly it's hard enough at this point to >> >deal with problems with the GNU getopt (awfully difficult to port >> >programs using GNU getopt without replicating the getopt() code >> >from glibc). At the same time, there are dozens of other Linux >> >compatibility issues. Putting all these new foreign library >> >calls into libc is not the solution unless we're interested in a >> >larger library. The argument "hardware is cheap" is not valid. >> >> Sounds to me like it's time to add these things to liblinuxcompat.a ? > > I don't see any liblinuxcompat. Are you proposing that one >should be created? yes. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6365.941230006>