From owner-freebsd-ppc@freebsd.org Thu Oct 10 16:34:32 2019 Return-Path: Delivered-To: freebsd-ppc@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 746FC1435D8 for ; Thu, 10 Oct 2019 16:34:32 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46pxWD2bFqz4Jpb; Thu, 10 Oct 2019 16:34:32 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 508B112173; Thu, 10 Oct 2019 16:34:32 +0000 (UTC) Date: Thu, 10 Oct 2019 16:34:32 +0000 From: Alexey Dokuchaev To: Kevin Smallman Cc: freebsd-ppc@freebsd.org Subject: Re: build 32-bit binary on powerpc64 Message-ID: <20191010163432.GB40333@FreeBSD.org> References: <20191010140937.GA89733@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191010140937.GA89733@FreeBSD.org> User-Agent: Mutt/1.11.4 (2019-03-13) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2019 16:34:32 -0000 On Thu, Oct 10, 2019 at 02:09:37PM +0000, Alexey Dokuchaev wrote: > On Thu, Oct 10, 2019 at 03:05:01PM +0100, Kevin Smallman wrote: > > There's one package I'd like to build in the ports tree that is 32-bit > > only, but I'm running the 64-bit version of FreeBSD powerpc on my old > > imac g5. If I go to the port's directory and just do 'make install' > > it naturally comes up with the error - 'This package is for i386 only, > > you are running powerpc64'. > > And we, of course, are expected to guess which is that port you're > talking about? :-) OK, apparently the problem is that `x11-toolkits/xview' port is currently marked as i386-only (back in r217128), I'd look into this shortly. ./danfe