Date: Fri, 29 Oct 1999 23:42:33 -0700 From: "David O'Brien" <obrien@freebsd.org> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: liblinuxcompat (was Re: stpcpy()) Message-ID: <19991029234233.A89583@dragon.nuxi.com> In-Reply-To: <Pine.BSF.4.10.9910292328410.82763-100000@green.myip.org>; from green@freebsd.org on Fri, Oct 29, 1999 at 11:29:47PM -0400 References: <19991029162024.A4314@futuresouth.com> <Pine.BSF.4.10.9910292328410.82763-100000@green.myip.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 1999 at 11:29:47PM -0400, Brian Fundakowski Feldman wrote: > For what it's worth, I'm pretty sure I proposed adding a glibc (originally > would've been gnu in my mind :) subdir in src/lib/compat. lib/compat/ is not the place for it. Only binaries go there. I assume you were proposing a FreeBSD version of glibc, not Linux one. If we do it, it should live in src/contrib/glibc and install as /usr/lib/libglibc.* > As libcompat is quite small, I'd rather leave libcompat for BSD stuff. I'm already on the verge of creating /usr/lib/libiberty, so let me spend some more time thinking how to deal with the GNU/Linux'isms. (especially since I'm already the point man on enough stuff in src/contrib/ that is affected by such things. I've decided to not add stpcpy() to our libc. I could easily create a /usr/lib/libgnu.a (libfsf/liblinuxcompat/libwhatever) that is always linked against by GCC. -- -- David (obrien@NUXI.com) 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?19991029234233.A89583>