From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sun, 26 Nov 2017 22:28:45 +0100 Subject: [Buildroot] [PATCH v2] vboot-utils: fix ARCH detection In-Reply-To: <20171111233903.5232e1f6@windsurf.home> (Thomas Petazzoni's message of "Sat, 11 Nov 2017 23:39:03 +0100") References: <20171107101715.GA26991@latitude.localdomain> <20171111233903.5232e1f6@windsurf.home> Message-ID: <87mv38enle.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Thomas" == Thomas Petazzoni writes: > Hello, > On Tue, 7 Nov 2017 12:17:15 +0200, Alex Suykov wrote: >> The package includes some target-specific code that is irrelevant >> in a host package but gets built anyway. The target for this code >> must be one of the supported ChromeOS targets. >> >> Supplied Makefile apparently relies on the environment to provide >> a valid target, with a simple fallback to host arch. This breaks >> the build if no value is provided and the host arch is not among >> the supported ones. >> >> Should fix >> http://autobuild.buildroot.net/results/d118a83b6c4f7f910d0d44c279f36251d7ba29e8/ >> and similar failures. >> >> Signed-off-by: Alex Suykov >> --- >> v2: Hard-coded ARCH=arm to avoid target restrictions in a host package. > Applied to master, thanks. Committed to 2017.02.x and 2017.08.x, thanks. -- Bye, Peter Korsgaard