From owner-freebsd-current@FreeBSD.ORG Sun Nov 7 14:19:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F08E16A4CE; Sun, 7 Nov 2004 14:19:03 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8961E43D2F; Sun, 7 Nov 2004 14:19:01 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 530502E5; Sun, 7 Nov 2004 15:19:00 +0100 (CET) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42614-03; Sun, 7 Nov 2004 15:18:59 +0100 (CET) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id 8B59B14A; Sun, 7 Nov 2004 15:18:59 +0100 (CET) From: Benjamin Lutz To: freebsd-ports@freebsd.org, freebsd-current@freebsd.org Date: Sun, 7 Nov 2004 15:18:47 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2231652.fMfnWbfZeF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411071518.59679.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Subject: Linux/i386 compat on Freebsd/amd64 / ONLY_FOR_ARCHS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Nov 2004 14:19:03 -0000 --nextPart2231652.fMfnWbfZeF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, This is a repost of a mail I sent to ports@ 3 weeks ago. I apologize if=20 that bothers anyone, but it didn't generate any replies, and the issue=20 remains unsolved. I've successfully managed to get Linux/i386 compatibility working on=20 =46reeBSD 5.3/amd64. Took some fiddling, but was actually less complicated= =20 that I assumed. I've written a short HOWTO, it's available here:=20 http://forums.bsdnexus.com/viewtopic.php?t=3D297 Now, one thing I noticed is that pretty much all linux ports are marked=20 with ONLY_FOR_ARCHS=3Di386, when in fact they work just fine on=20 =46reeBSD/amd64 (with the linux/i386 compatibility environment, ie=20 linux_base-8 installed). This is somewhat annoying,as it requires=20 manually setting MACHINE_ARCH=3Di386 and sometimes ARCH=3Di386 with every=20 make. Now... I assume that eventually FreeBSD will also get Linux/*64 support=20 sooner or later, and that there'll be linux ports that use only one of=20 the two linux compat environments. So what I'm trying to say is that I'm not sure that setting ONLY_FOR_ARCHS= =20 for binary linux ports makes a lot of sense... could it not be assumed=20 that if the linux/i386 compatibility environment is installed on a=20 machine, linux/i386 apps will work even if this is not an i386 machine?=20 Same thing when FreeBSD gets linux/*64 support. Unfortunately, I'm not familiar enough with the internals of the ports=20 system to come up with an ingeniously simple but powerful solution (nor=20 am I ingenious enough ;) ), but maybe I can start a discussion that leads=20 to something good? Benjamin --nextPart2231652.fMfnWbfZeF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBji7TgShs4qbRdeQRAq0OAJ0QtImOVXbdzAv3Q5OFsDqpH5yC9wCfTHS2 vYMMUqgsx9hKy1PdsGX9uAQ= =vAqM -----END PGP SIGNATURE----- --nextPart2231652.fMfnWbfZeF--