Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Jun 2014 14:56:10 -0400
From:      Chris Ross <cross+freebsd@distal.com>
To:        Brooks Davis <brooks@freebsd.org>
Cc:        freebsd-stable@freebsd.org, Peter Wemm <peter@wemm.org>
Subject:   Re: Cross-building FreeBSD core...
Message-ID:  <9FEA3011-7E8F-4AB3-A70E-7ACCB5286E36@distal.com>
In-Reply-To: <20140609185022.GD94040@lor.one-eyed-alien.net>
References:  <FB1DB8CA-F1D1-4339-B238-F08704EDDA75@distal.com> <2158607.RZmBJ56eyy@overcee.wemm.org> <20140609185022.GD94040@lor.one-eyed-alien.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Jun 9, 2014, at 14:50, Brooks Davis <brooks@freebsd.org> wrote:
>> I don't know if it's still the case, but MAKEOBJDIRPREFIX used to =
have to be=20
>> set before calling make, ie something more like:
>> env MAKEOBJDIRPREFIX=3D/home/cross/obj.amd64 make buildworld =
TARGET=3Damd64=20
>> TARGET_ARCH=3Damd64
>=20
> It is.  Setting MAKEOBJDIRPREFIX as a make argument means it can't be
> changed and apparently that ability is used somewhere in the bootstrap
> process.  The symptoms are bizzare and you end up with a cross built
> make_keys in the native tools path.
>=20
> Adding a seatbelt to detect this case and fail is on my todo list.

  Excellent.  Thank you fellows very much.  I will re-run with that =
variable in my
environment.  Thanks for the info!

               - Chris





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9FEA3011-7E8F-4AB3-A70E-7ACCB5286E36>