From owner-freebsd-questions Tue Apr 21 14:18:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26618 for freebsd-questions-outgoing; Tue, 21 Apr 1998 14:18:44 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26421 for ; Tue, 21 Apr 1998 21:18:12 GMT (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id OAA04472; Tue, 21 Apr 1998 14:18:04 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 21 Apr 1998 14:18:04 -0700 (PDT) From: Doug White Reply-To: Doug White To: Lynn Gazis cc: questions@FreeBSD.ORG, Ken Greer Subject: Re: FreeBSD and BSDI binary compatibility In-Reply-To: <9804212050.AA18291@elan.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Apr 1998, Lynn Gazis wrote: > > > > I don't think so. Our libc is pretty unique. If you statically link it > > you have a better chance of it working -- then it depends purely on the > > system calls. > > If this is a link issue, will supplying object files and linking them > on BSDi work (because that is, actually, the ultimate goal). No, it's a shared lib issue. BSDi's libc doesn't contain the same functions as ours. > They already have that platform, and are supporting customers who have > it. We supply software that gets integrated into other people's software > (which is why taking the objects from FreeBSD and linking them on BSDi > might actually be a reasonable solution, if it is something which is > feasible). I suppose you could try it, as long as you know where different functions live. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message