From owner-freebsd-stable@FreeBSD.ORG  Mon Jun  9 18:58:00 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8B70BAEE;
 Mon,  9 Jun 2014 18:58:00 +0000 (UTC)
Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4AE87263A;
 Mon,  9 Jun 2014 18:58:00 +0000 (UTC)
Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25])
 (authenticated bits=0)
 by hydra.pix.net (8.14.8/8.14.8) with ESMTP id s59Ivl1R041247;
 Mon, 9 Jun 2014 14:57:54 -0400 (EDT)
 (envelope-from cross+freebsd@distal.com)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.1 at mail.pix.net
Received: from zalamar.mm-corp.net ([65.207.51.191]) (authenticated bits=0)
 by mail.distal.com (8.14.8/8.14.8) with ESMTP id s59IuP9E029776
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
 Mon, 9 Jun 2014 14:56:26 -0400 (EDT)
 (envelope-from cross+freebsd@distal.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Cross-building FreeBSD core...
From: Chris Ross <cross+freebsd@distal.com>
In-Reply-To: <20140609185022.GD94040@lor.one-eyed-alien.net>
Date: Mon, 9 Jun 2014 14:56:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FEA3011-7E8F-4AB3-A70E-7ACCB5286E36@distal.com>
References: <FB1DB8CA-F1D1-4339-B238-F08704EDDA75@distal.com>
 <2158607.RZmBJ56eyy@overcee.wemm.org>
 <20140609185022.GD94040@lor.one-eyed-alien.net>
To: Brooks Davis <brooks@freebsd.org>
X-Mailer: Apple Mail (2.1827)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mail.distal.com [206.138.151.250]); Mon, 09 Jun 2014 14:56:26 -0400 (EDT)
Cc: freebsd-stable@freebsd.org, Peter Wemm <peter@wemm.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jun 2014 18:58:00 -0000


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