From owner-freebsd-current@freebsd.org Mon Jan 25 23:16:59 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAF62A46609 for ; Mon, 25 Jan 2016 23:16:59 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9AD9B0C for ; Mon, 25 Jan 2016 23:16:59 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTP id u0PNGwQr016783 for ; Mon, 25 Jan 2016 18:16:58 -0500 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Mon, 25 Jan 2016 18:16:58 -0500 (EST) Date: Mon, 25 Jan 2016 18:16:58 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: freebsd-current@freebsd.org Subject: Re: Cross-building for i386 from amd64 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2016 23:16:59 -0000 On Mon, 25 Jan 2016, Daniel Eischen wrote: > Is cross-building world for i386 from amd64 suppose to work? > > It doesn't in -stable. From reading the documentation out there, > one of these should work: > > make TARGET=i386 buildworld > make TARGET_ARCH=i386 buildworld > > What incantations do I need? The end result is I want multiple > developers to be able to build nanobsd i386 images from amd64. I guess you can ignore this, I seemed to have hit a real compilation bug in -stable, which updating to the most recent -stable has fixed. FYI, I used: make TARGET_ARCH=i386 -j4 buildworld in -stable, and that worked. -- DE