From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] glibc: ensure BR2_MAKE is also used for subdirs
Date: Tue, 20 Nov 2018 08:18:05 +0100 [thread overview]
Message-ID: <87tvkcp68i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181119162515.20360-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 19 Nov 2018 17:25:13 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> The configure script contains logic to figure out what make program to
> invoke for subdirectories (trying gnumake, gmake, make). Explicitly force
> it to use our BR2_MAKE to ensure the right make version is used.
> As GLIBC_CONF_ENV is only initialized below, move this section below it.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> v3: No changes
> v2:
> - Fix CONV/CONF typo, move section below GLIBC_CONF_ENV initialization
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-11-20 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 16:25 [Buildroot] [PATCH v3 1/3] glibc: ensure BR2_MAKE is also used for subdirs Peter Korsgaard
2018-11-19 16:25 ` [Buildroot] [PATCH v3 2/3] make: drop gnumake/gmake aliases for host-make Peter Korsgaard
2018-11-20 7:18 ` Peter Korsgaard
2018-11-20 7:22 ` yann.morin at orange.com
2018-11-19 16:25 ` [Buildroot] [PATCH v3 3/3] make: configure host-make with host- prefix Peter Korsgaard
2018-11-20 7:18 ` Peter Korsgaard
2018-11-20 7:32 ` yann.morin at orange.com
2018-11-20 7:18 ` Peter Korsgaard [this message]
2018-11-20 7:18 ` [Buildroot] [PATCH v3 1/3] glibc: ensure BR2_MAKE is also used for subdirs yann.morin at orange.com
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=87tvkcp68i.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.