Date: Fri, 10 May 2002 01:13:52 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: "Michael C. Wu" <keichii@iteration.net> Cc: obrien@freebsd.org, Matthew Dillon <dillon@apollo.backplane.com>, arch@FreeBSD.ORG Subject: Re: syscall changes to deal with 32->64 changes. Message-ID: <XFMail.20020510011352.jhb@FreeBSD.org> In-Reply-To: <20020510045701.GA34750@nuit.iteration.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10-May-2002 Michael C. Wu wrote: > On Tue, May 07, 2002 at 01:13:14PM -0700, David O'Brien scribbled: >| On Tue, May 07, 2002 at 12:40:43PM -0700, Matthew Dillon wrote: >| > the way for us to allow natively compiled multi-architectural support. >| > e.g. consider this: >| > cc -ABI4 ... >| > cc -ABI5 ... >| > cc -ABILinux ... >| > cc -ABIOpenBSD ... >| Honestly, why do we have this need? It seems to fall into the "it would >| be nice"; but seldomly used. > > Vendor imported code (e.g. KAME(sigh..), USB, possibly 1394, > cardbus, possibly some userland important tools and libraries) > would have little or no diffs from the original vendor's code.. Erm, all the changes so far aren't in API's, but rather changing the size of types like time_t. The same KAME code would compile fine. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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.20020510011352.jhb>