From owner-freebsd-questions@FreeBSD.ORG Mon Mar 5 16:55:59 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5C8E1065672 for ; Mon, 5 Mar 2012 16:55:59 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 69A518FC16 for ; Mon, 5 Mar 2012 16:55:59 +0000 (UTC) Received: from r56.edvax.de (port-92-195-185-71.dynamic.qsc.de [92.195.185.71]) by mx01.qsc.de (Postfix) with ESMTP id 4148E3CD5D; Mon, 5 Mar 2012 17:55:51 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id q25GtpsO002579; Mon, 5 Mar 2012 17:55:51 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Mon, 5 Mar 2012 17:55:51 +0100 From: Polytropon To: Bernt Hansson Message-Id: <20120305175551.ae24b6f0.freebsd@edvax.de> In-Reply-To: <4F54ED12.1090409@bananmonarki.se> References: <4F547C59.1040604@bananmonarki.se> <4F548571.1050203@gmail.com> <4F54ED12.1090409@bananmonarki.se> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: port to package amd64 to i386 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 16:55:59 -0000 On Mon, 05 Mar 2012 17:42:58 +0100, Bernt Hansson wrote: > Thank you for the pointer. I do find it a bit overkill to setup jails > and such, just to build a few ports. The "problem" here is that a specific build environment is required. > I was thinking more along the line of; > > cd /usr/ports/"random port" > > make "it for i386 even if we are building it on amd64, ooh by the way > build it as a package, and all dependencies as packages as well" Again, a "problem" is that packages can only be generated if the port has been installed, which is the "make package" task typically following "make install", resulting in the desired package in the /usr/ports/packages/ subtree. See "man ports" regarding the "package" target. I think that _could_ be overridden by specifying a different, "temporary" $PREFIX to install to, but I haven't tested this approach. For the dependencies, I think there was a setting to be included in /etc/make.conf... MAKE_DEPENDS=PACKAGE? Something like this will cause all dependencies to be built and archived as a package. > Oh man, man ports. But I do not find the flag > -build-for-another-system-cpu-whatever Some settings can be transferred to the make environment, usually /etc/make.conf is used. > Can the ports system be (ab)used in that way? I don't think it is that easy. :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...