Date: Fri, 29 Oct 1999 13:45:49 -0500 From: Chris Costello <chris@calldei.com> To: Warner Losh <imp@village.org> Cc: obrien@freebsd.org, freebsd-arch@freebsd.org Subject: Re: stpcpy() Message-ID: <19991029134549.B535@holly.calldei.com> In-Reply-To: <199910291829.MAA89401@harmony.village.org> References: <19991029132257.A535@holly.calldei.com> <19991029111352.A87934@dragon.nuxi.com> <19991029132257.A535@holly.calldei.com> <199910291829.MAA89401@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 1999, Warner Losh wrote: > In message <19991029132257.A535@holly.calldei.com> Chris Costello writes: > : I'm seeing more and more of a need for a compat library for > : Linux and GNU software in general. Adding unnecessary bloat to > : our libc isn't necessary, in my opinion. > > The problem with this is that it becomes harder to build on FreeBSD > because you have to add additional, non-standard libraries to the > build process. This is the fault of the author of the tool, since > they used non-standard interfaces, so maybe it wouldn't be too bad. > The risk we run in not supporting them in libc is the perception that > FreeBSD isn't compatible (never mind what the sstandards say). That's the problem. I honestly can't begin to think of a perfect way of getting around Linux developers putting kludge after kludge on top of poorly written workarounds on top of hacks that were never really fully implemented (as far as libc goes). Put their functions in our libc and we end up with a bigger, bloated libc. Make a new library and cause trouble for people wanting to build the latest greatest Linux program on FreeBSD. -- |Chris Costello <chris@calldei.com> |Your fault, core dumped. `---------------------------------- 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?19991029134549.B535>