From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [2/2] package/glibc: bump to version 2.28
Date: Wed, 15 Aug 2018 21:16:00 +0200 [thread overview]
Message-ID: <87wosra1an.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180815134041.74b55316@windsurf> (Thomas Petazzoni's message of "Wed, 15 Aug 2018 13:40:41 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> On Wed, 15 Aug 2018 09:19:53 +0300, Baruch Siach wrote:
>> Romain Naour writes:
>> > https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html
>>
>> This announcement says:
>>
>> GNU make 4.0 or later is now required to build glibc.
>>
>> autobuilders now show that:
>>
>> http://autobuild.buildroot.net/?reason=glibc-glibc-2.28
>>
>> Since glibc is a fundamental package, does that mean we need to bump the
>> make version requirement to 4.0 (current requirement is 3.81)? Maybe
>> build host-make on older hosts?
> Building host-make on machines that don't have make >= 4.0 sounds like
> a good approach to me. And of course, we only do this as a dependency
> of glibc.
Agreed, it is imho too early to require make >= 4.0 globally.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-08-15 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 18:14 [Buildroot] [PATCH 1/2] package/systemd: fix statx support with glibc >= 2.28 Romain Naour
2018-08-03 18:14 ` [Buildroot] [PATCH 2/2] package/glibc: bump to version 2.28 Romain Naour
2018-08-09 21:58 ` Thomas Petazzoni
2018-08-15 6:19 ` [Buildroot] [2/2] " Baruch Siach
2018-08-15 11:40 ` Thomas Petazzoni
2018-08-15 19:16 ` Peter Korsgaard [this message]
2018-08-25 15:34 ` Romain Naour
2018-08-09 21:57 ` [Buildroot] [PATCH 1/2] package/systemd: fix statx support with glibc >= 2.28 Thomas Petazzoni
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=87wosra1an.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox