From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 19:42:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB57E16A4D6 for ; Wed, 24 Nov 2004 19:42:18 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9EC343D49 for ; Wed, 24 Nov 2004 19:42:18 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAOJgdQX028092; Wed, 24 Nov 2004 11:42:39 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAOJgdV9028090; Wed, 24 Nov 2004 11:42:39 -0800 Date: Wed, 24 Nov 2004 11:42:39 -0800 From: Brooks Davis To: Chuck Robey Message-ID: <20041124194239.GB24353@odin.ac.hmc.edu> References: <20041124145143.O4002@april.chuckr.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: <20041124145143.O4002@april.chuckr.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-amd64@freebsd.org Subject: Re: acroread on the amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Nov 2004 19:42:20 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 24, 2004 at 02:57:07PM -0500, Chuck Robey wrote: > I noticed that acroread is marked as being only for the i386 ... I have a > question about that ... I'm a little new at running the amd64, but I > thought that it was compatible (if it had the 32 bit libraries installed > to support it) with i386, so I would have expected my amd64 machine to be > ablel to run acroread with little trouble. The port being marked > as"ONLY_FOR_ARCHS", well, I considered, *possibly*, that the port author > hadn't had the testing capability, and maybe it did too work on the amd64. If you get 32-bit linux compatability running then acrobat should work. This is actually a deficencly in our ports infrastructure. For binary only ports, we could really use the ability to say that the port supports the following native architectures and the system should be smart enough to know that i386 ports will work on amd64. > Anyone have more detailed info about that? Notice, I didn't mail to > freeBSD-ports, I don't know how strict our mailing list filters are, I > thought they'd probably kick me out if I tried to cross-post. A single cross post will work. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --9zSXsLTf0vkW971A Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBpOQvXY6L6fI4GtQRAgBdAKCrHjhzyg3mHBwNinMui/NhtPMS2QCfVfJq Jr6SAeOxXBZnW+3YGChKryg= =C3Zi -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A--