Date: Sat, 12 Mar 2016 00:30:26 +0100 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: poudriere and MAKEOBJDIRPREFIX Message-ID: <20160312003026.7017eb24.ohartman@zedat.fu-berlin.de> In-Reply-To: <56E3049A.6080402@FreeBSD.org> References: <20160310143739.3c21bbac@hermann> <56E3049A.6080402@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/wQX1B=ZAImXeZWwtACmgh5W Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 11 Mar 2016 09:47:06 -0800 Bryan Drewery <bdrewery@FreeBSD.org> schrieb: > On 3/10/2016 5:37 AM, O. Hartmann wrote: > > env MAKEOBJDIRPREFIX=3D/some/place poudriere jail -c -j 10-stable-amd64= \ > > -a amd64 -v stable/10 -m src=3D/somesrc/srcplace/ > >=20 > > In poudriere.conf I added=20 > >=20 > > export MAKEOBJDIRPREFIX=3D$MAKEOBJDIRPREFIX > >=20 > > as recommended in some posts I found googling for a solution. Please > > have in mind that I use csh - the export and poudriere's environment is > > obviously sh. > >=20 > > This fails, the PATH is always cut down to /somesrc/srcplace/, missing > > the prepending portion taken from MAKEOBJDIRPREFIX - it is set to zero > > length it seems. Ommitting env MAKEOBJDIRPREFIX=3D/some/place to the > > poudriere command as shown above results in "usr/obj" being prepended. > > This seems odd! > >=20 > > The only sollution to this was to give the specific jail its private > > 10-stable-amd64-poudriere.conf. But this seems to be not the correct > > way to do so, since MAKEOBJDIRPREFIX is supposed to be set in the > > environment. > >=20 > > What am I missing here? =20 >=20 > The poudriere command clears the environment except for PATH and TERM. > A 10-stable-amd64-poudriere.conf with export MAKEOBJDIRPREFIX=3Dvalue > would work. >=20 Thank you Bryan. Indeed, it worked that way. It would be great if there would be a hint some= where in the docs or in the example poudriere.conf file. I found no hint whether compilation/building packages on a base system runn= ing a fifferent major release that the jail would work or not - it is made clear,= that within a major release, the head or most recent of the release is capable to build= minors of the same major release due to ABI/KABI compatibility. What is about the recent CURRENT as host with 10.X-Rel or 10-stable jails? I have problems building lang/python27 within the 10-stable jail. The build= fails in the stagin phase with "bad c++ code". A natural "make" build on CURRENT works f= lawlessly. The config of the 10-stable jail is "vanilla". Regards and thanks, Oliver=20 --Sig_/wQX1B=ZAImXeZWwtACmgh5W Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW41USAAoJEOgBcD7A/5N8IisIANE55BIk/VYXW8GSnA65NRfh liKs1C+07kpPRFhBceMPDFv0Nw/aDOwN9cK82DLeiYKIkDLeP1GSbX1ejP8uD+F6 bznMocSSFjFEl3gp7HU6LemJDA0qXWmG+PRs+K9hkt8hXxHIJfMyehmYPI5UMTqy iBtq3A+XK8alamUx2SjurF+lQukwT1MIvxpIHOek2t9W2e3cuOCcH52RV9Llzjrm 6hGrPeg3Zh41CcDkPluk9pDvg7bmykzeTGyRqjuX4t1f+sWo95bV0vsOfhBEySPc jCq4o79bPPxo5W6A/Ji5A/MFljihAhESLk4nDGTsKqqVU2Vzc7Th2zV33QryLCc= =ujob -----END PGP SIGNATURE----- --Sig_/wQX1B=ZAImXeZWwtACmgh5W--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160312003026.7017eb24.ohartman>