Date: Thu, 9 May 2002 21:57:01 -0700 From: "Michael C. Wu" <keichii@iteration.net> To: arch@FreeBSD.ORG Cc: Matthew Dillon <dillon@apollo.backplane.com>, obrien@freebsd.org Subject: Re: syscall changes to deal with 32->64 changes. Message-ID: <20020510045701.GA34750@nuit.iteration.net> In-Reply-To: <20020507131314.B29014@dragon.nuxi.com> References: <XFMail.20020507140110.jhb@FreeBSD.org> <200205071940.g47Jehl84130@apollo.backplane.com> <20020507131314.B29014@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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..
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?20020510045701.GA34750>