From owner-freebsd-current Sun Oct 4 17:42:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26468 for freebsd-current-outgoing; Sun, 4 Oct 1998 17:42:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26450 for ; Sun, 4 Oct 1998 17:42:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA07872; Sun, 4 Oct 1998 17:46:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810050046.RAA07872@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), cracauer@cons.org, chuckr@mat.net, nate@mt.sri.com, osa@etrust.ru, current@FreeBSD.ORG Subject: Re: What about jdk-1.1.6 for FreeBSD-3.0-ELF ? In-reply-to: Your message of "Mon, 05 Oct 1998 00:08:44 -0000." <199810050008.RAA09541@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 1998 17:46:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The Solaris ABI defines the interface between executing programs and the > > kernel. > > > > The various programming APIs define the source-level interface. > > > > There are no standards for the interface between shared objects which > > are relevant to the discussion. > > Sure there are. There's the Solaris ABI. Read what I just wrote: The Solaris ABI specifies the interface between a running program and the kernel. It *does*not* specify the interfaces between eg. libc and a libc consumer. The Solaris API specifies this at the *source* level. > > You will notice, if you had been paying attention to the list of > > missing library symbols recently posted, that the interface between the > > Solaris Motif library and the Solaris C library involves a not > > insubstantial number of very weird symbols. It might be feasible to > > implement a compatibility library, but this would, naturally, suck. > > How? In that it would allow shared Solaris binaries to operate on > FreeBSD? No, it would allow libraries built to link against the Solaris libc to instead link with the FreeBSD libc. > You must have a different definition of "suck"... The practical issues involved in implementing such a shim would be disgusting. We already have a mechanism for allowing Solaris binaries to operate on FreeBSD; it will be committed shortly after 3.0 is released. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message