From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 24 20:01:55 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 8890F16A4CE for ; Wed, 24 Nov 2004 20:01:55 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B8F43D54 for ; Wed, 24 Nov 2004 20:01:54 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao03.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041124200154.MHTY14730.lakermmtao03.cox.net@dolphin.local.net>; Wed, 24 Nov 2004 15:01:54 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAOK1rgV078919; Wed, 24 Nov 2004 14:01:53 -0600 (CST) (envelope-from conrads@cox.net) Date: Wed, 24 Nov 2004 14:01:48 -0600 From: "Conrad J. Sabatier" To: Brooks Davis Message-ID: <20041124140148.61926075@dolphin.local.net> In-Reply-To: <20041124194239.GB24353@odin.ac.hmc.edu> References: <20041124145143.O4002@april.chuckr.org> <20041124194239.GB24353@odin.ac.hmc.edu> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 20:01:55 -0000 On Wed, 24 Nov 2004 11:42:39 -0800, Brooks Davis wrote: > 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. Not only should, but actually does. :-) > 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. Yes, I've tinkered with a number of ONLY_FOR_ARCHS ports on amd64, and gotten them to build and run successfully. I really should send-pr these (if I can remember now which ones they were). :-) -- Conrad J. Sabatier -- "In Unix veritas"