Date: Mon, 5 Mar 2012 17:55:51 +0100 From: Polytropon <freebsd@edvax.de> To: Bernt Hansson <bah@bananmonarki.se> Cc: freebsd-questions@freebsd.org Subject: Re: port to package amd64 to i386 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120305175551.ae24b6f0.freebsd>