From owner-freebsd-arch Thu May 9 23:56:38 2002 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DA02737B40C; Thu, 9 May 2002 23:56:35 -0700 (PDT) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.3/8.9.1) with ESMTP id g4A6uZhU031060; Thu, 9 May 2002 23:56:35 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.3/8.12.3/Submit) id g4A6uZgF031059; Thu, 9 May 2002 23:56:35 -0700 (PDT) Date: Thu, 9 May 2002 23:56:35 -0700 (PDT) From: Matthew Dillon Message-Id: <200205100656.g4A6uZgF031059@apollo.backplane.com> To: John Baldwin Cc: "Michael C. Wu" , obrien@FreeBSD.org, arch@FreeBSD.org Subject: Re: syscall changes to deal with 32->64 changes. References: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :> :> 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 <>< http://www.FreeBSD.org/~jhb/ Huh? Changing the size of time_t sure sounds like an API change to me! . Which was my original point... though I was considering those ports which might not be 64-bit-time_t friendly (probably hundreds). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message