From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis results for 2018-10-09
Date: Thu, 11 Oct 2018 16:12:31 +0200 [thread overview]
Message-ID: <20181011161231.5d4bf9cd@windsurf> (raw)
In-Reply-To: <87efcwstjt.fsf@dell.be.48ers.dk>
Hello,
+Romain Naour in Cc, since he added host-make to fix the glibc build.
On Thu, 11 Oct 2018 11:48:22 +0200, Peter Korsgaard wrote:
> > Yes, I figured that out after sending my summary. I reproduced the
> > issue on my build server, which has an old make installed system-wide,
> > and this issue seems to appear only when host-make is built prior to
> > boa. There's a mixup of make being used, with a new "make" used at the
> > top-level, passing options unknown to the old "make" used at the
> > lower-level.
>
> Ahh, yes. It looks to be the other way around though:
Yeah, maybe, I didn't look closely, and I assumed the old version of
make is the one that didn't support the --jobserver-fds option.
Apparently, it's the opposite.
> usr/bin/make -j6 -C /home/peko/autobuild/instance-0/output/build/boa-0.94.14rc21/
> make[1]: Entering directory `/home/peko/autobuild/instance-0/output/build/boa-0.94.14rc21'
> (cd src && make -w --jobserver-fds=5,6 -j)
> make: unrecognized option '--jobserver-fds=5,6'
>
> So the issue is that we expand the path to make on the host in
> package/Makefile.in:HOSTMAKE but then host-make installs make into the
> path and build systems just calling make instead of looking at the MAKE
> variable (which boa does because of its gnumake check) ends up with
> host-make rather than the system one.
>
> A quick fix would be to set BOA_MAKE to $(BR2_MAKE), but that is a bit
> of a hack.
Perhaps we need to think about a more global solution. How do we want
to use host-make ? If it's compiled, should it be used to build all
packages ? Should it only be used for glibc ? In the latter case, how
do we "hide" it from all packages, and make it used only by glibc ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-11 14:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-10-09 Thomas Petazzoni
2018-10-10 15:48 ` [Buildroot] Analysis " Thomas Petazzoni
2018-10-10 16:28 ` Matthew Weber
2018-10-10 17:57 ` Fabrice Fontaine
2018-10-10 19:14 ` Thomas Petazzoni
2018-10-10 21:25 ` Matthew Weber
2018-10-11 6:50 ` Thomas Petazzoni
2018-10-11 13:35 ` Matthew Weber
2018-10-12 3:57 ` Matthew Weber
2018-10-12 14:16 ` Matthew Weber
2018-10-20 14:10 ` Matthew Weber
2018-10-10 19:05 ` Thomas Petazzoni
2018-10-12 16:00 ` Matthew Weber
2018-10-10 21:30 ` Arnout Vandecappelle
2018-10-11 6:46 ` Thomas Petazzoni
2018-10-11 9:21 ` Peter Korsgaard
2018-10-11 21:32 ` Arnout Vandecappelle
2018-10-10 21:35 ` Arnout Vandecappelle
2018-10-12 6:54 ` Jörg Krause
2018-10-10 21:52 ` Christian Stewart
2018-10-10 21:54 ` Arnout Vandecappelle
2018-10-11 4:43 ` Baruch Siach
2018-10-11 6:53 ` Thomas Petazzoni
2018-10-11 9:48 ` Peter Korsgaard
2018-10-11 14:12 ` Thomas Petazzoni [this message]
2018-10-11 15:25 ` Peter Korsgaard
2018-10-11 8:39 ` Thomas Petazzoni
2018-10-11 10:42 ` Peter Korsgaard
2018-10-11 11:08 ` Baruch Siach
2018-10-11 11:18 ` Peter Korsgaard
2018-10-11 11:45 ` Baruch Siach
2018-10-11 12:46 ` Peter Korsgaard
2018-10-11 11:02 ` Giulio Benetti
2018-10-20 15:22 ` Giulio Benetti
2018-10-11 14:31 ` Frank Hunleth
2018-10-11 14:32 ` Thomas Petazzoni
2018-10-11 19:24 ` Giulio Benetti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181011161231.5d4bf9cd@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.