From owner-freebsd-ports@FreeBSD.ORG Thu Mar 31 16:05:40 2005 Return-Path: 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 4075016A4CE for ; Thu, 31 Mar 2005 16:05:40 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C4E43D3F for ; Thu, 31 Mar 2005 16:05:39 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so574912wri for ; Thu, 31 Mar 2005 08:05:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=pSBCCJ19+N75p54pz05OyZjhWbiGd8L+z8s05OowpEAqaonE/3Zn7XP6XU7t7fb/r5FF0ZMbgpsHxdI79/noqjuIX9HgFv4wvALD1V1qE6RGf6L0Q7+OiZkf5eTBHJArjzYjSJFZ5bfmcRovgOh6p+mx77IUdpUwijUPs6N5PXQ= Received: by 10.54.3.35 with SMTP id 35mr1049466wrc; Thu, 31 Mar 2005 08:05:38 -0800 (PST) Received: by 10.54.29.77 with HTTP; Thu, 31 Mar 2005 08:05:37 -0800 (PST) Message-ID: <790a9fff050331080572081eb6@mail.gmail.com> Date: Thu, 31 Mar 2005 10:05:37 -0600 From: Scot Hetzel To: Michael Hopkins In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: cc: freebsd-ports-bugs@freebsd.org cc: freebsd-emulation@freebsd.org cc: freebsd-ports@freebsd.org cc: "freebsd-amd64@freebsd.org" Subject: Re: Working and broken Linux ports on amd64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Mar 2005 16:05:40 -0000 On Thu, 31 Mar 2005 12:14:47 +0100, Michael Hopkins wrote: > In general > ---------- > A lot of Linux ports are giving this message which I suspect may not always > be appropriate: > > ...is only for i386, and you are running amd64. > For the ports that are giving you that message, try adding amd64 to the ONLY_FOR_ARCHS variable, and try to install and run the program. If it works, submit a PR with a patch to update the port. This is the only way we'll know if it works on the amd64. Scot