From owner-freebsd-ports@FreeBSD.ORG Sat Nov 19 19:32:37 2005 Return-Path: X-Original-To: ports@FreeBSD.Org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B5C416A41F for ; Sat, 19 Nov 2005 19:32:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 283B143D49 for ; Sat, 19 Nov 2005 19:32:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 099CF1A3C1C; Sat, 19 Nov 2005 11:32:37 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 40F6B51265; Sat, 19 Nov 2005 14:32:36 -0500 (EST) Date: Sat, 19 Nov 2005 14:32:36 -0500 From: Kris Kennaway To: K?vesd?n G?bor Message-ID: <20051119193236.GA89234@xor.obsecurity.org> References: <437F20AA.2050901@t-hosting.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <437F20AA.2050901@t-hosting.hu> User-Agent: Mutt/1.4.2.1i Cc: ports@FreeBSD.Org Subject: Re: How to set ONLY_FOR_ARCH for binary ports? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2005 19:32:37 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 19, 2005 at 01:55:06PM +0100, K?vesd?n G?bor wrote: > Hello, >=20 > I haven't found this in Porter's Handbook. How should I set=20 > ONLY_FOR_ARCHS in a port that installs i386 binaries? The amd64=20 > architecture, and IIRC ia64 too, have compatibility layers for i386=20 > architecture, but it isn't necessarily installed. Can I set=20 > ONLY_FOR_ARCH to "i386 amd64 ia64"? Or is there any way to check whether= =20 > the compatibility layer is available? Set it to i386 amd64 (preferably you should actually test that it's usable on amd64 first)..ia64 doesn't seem to have good enough compatibility. Kris --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDf33TWry0BWjoQKURAi60AKDxoQ8CdDVLE5/WJyxg8b91zTabYwCgu+xg ZNIK5JNlTKE4IVmIsu6Bgi0= =fJRj -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--