From owner-freebsd-emulation Wed Jan 12 18:31:29 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 34B8414D77 for ; Wed, 12 Jan 2000 18:31:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA03580 for ; Wed, 12 Jan 2000 18:38:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001130238.SAA03580@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-emulation@FreeBSD.ORG Subject: Re: DUAL-brand ELF binaries In-reply-to: Your message of "Thu, 13 Jan 2000 02:34:30 +0100." <200001130134.CAA61708@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2000 18:38:31 -0800 From: Mike Smith Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Martin v.Loewis wrote in list.freebsd-emulatio= n: > > Sure there is. On Linux, "int 0x80" performs a system call. You can > > emit this instruction either directly (via assembler code), or via > > the _syscall macros from . > = > But is that the usual, common and recommended way to issue > syscalls? That's one perfectly legitimate way of doing it, yes. However, the real issue here is not system calls, it's the binary = interface to libc. If the third-party library binds to anything other = than a clearly defined interface layer in the application, ie. it makes = any calls at all into libc, the chances are good that it will fail = because the interface to libc is defined at the source level, not the = binary level. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message