From owner-freebsd-java Tue Jan 26 14:27:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10253 for freebsd-java-outgoing; Tue, 26 Jan 1999 14:27:10 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10247 for ; Tue, 26 Jan 1999 14:27:09 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA26131; Tue, 26 Jan 1999 15:26:40 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA14679; Tue, 26 Jan 1999 15:26:38 -0700 Date: Tue, 26 Jan 1999 15:26:38 -0700 Message-Id: <199901262226.PAA14679@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: Nate@primenet.com, Williams@primenet.com, , Mats@primenet.com, Lofkvist@primenet.com, , java@FreeBSD.ORG Subject: Re: TowerJ for FreeBSD In-Reply-To: <199901262216.PAA01731@usr07.primenet.com> References: <199901262216.PAA01731@usr07.primenet.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > And how hard is it to add a feature allowing a FreeBSD binary (java) > > > load and run a Solaris shared library (the Solaris JIT) with/without > > > Solaris binary compatibility to begin with? > > > > Really hard. Hard enough that it will probably never be done. See > > postings on hackers on this where Terry Lambert bogusly declared it was > > trivial without understanding the details. > > The library is ELF, and is unrelocated, so it isn't Solaris specific > excepet for partially preresolved jump table vector names. Wrong. It makes Solaris system calls, using Solaris parameters and Solaris defines. > In general, the dependency is that most of these libraries are linked > against the Solais libc, and bring in symbols from there. Right. A FreeBSD 'binary' can't make Solaris libc calls correctly. > For example, a number of people have been using the Solaris CDE ELF > library to get an ELF Motif 2.0 implementation that they can link > against, since Sun used to offer the thing for download from their > WWW site, and you can get it on the Solaris "free" ($15) CDROM. Nobody has been using the Solaris CDE ELF library to build FreeBSD binaries. As was pointed a while back, you can't 'mix' a Solaris library and a FreeBSD binary. I'd even buy you dinner if you can make anything beyond a simple toy application work with the Solaris library. I've got a FreeBSD native application that uses Motif. I'll bet you dinner that you can't make it work with the Solaris ELF library. > It's pretty trivial (contrary to Nate's claims) to find the list of > interfaces affected by just truing to link the Motif library > directly. You'll get a list of unresolved externals. Prove it. Really, I'd love for you to prove me wrong. Hand-waving a long email messages stating that it's trivial mean nothing when in fact it doesn't work. Issues such as system calls (which are the biggest problem), different library functions, etc.. can all be worked around, but not 'trivialy'. If SVR4/Solaris emulation was a worthwhile goal, someone could continually maintain it like we do with the Linux emulation, but the fact of the matter is that it's not worth it (both in terms of the code required as well as the complexity in trying to switch to 'Solaris' mode from 'FreeBSD' mode and back in a single binary.) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message