Date: Sun, 31 Oct 1999 16:43:59 +0930 (CST) From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Warner Losh <imp@village.org> Cc: freebsd-arch@freebsd.org, obrien@freebsd.org, chris@calldei.com Subject: Re: stpcpy() Message-ID: <XFMail.991031164359.doconnor@gsoft.com.au> In-Reply-To: <199910291829.MAA89401@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29-Oct-99 Warner Losh wrote: > 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). Well if you have a port which has this stuff in it (stpcpy, getopt, etc) then where's the problem? If you are building by hand adding -I/usr/local/include and -lcompatlinux to your makefile is easy, and if its a port its transparent to the end user. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum 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?XFMail.991031164359.doconnor>