From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] host-localedef: Compile against glibc-2.29
Date: Tue, 25 Jun 2019 08:16:54 +0200 [thread overview]
Message-ID: <87a7e6jijt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <cab0e23381beef9e4f8d9e895e6025c110cd2abd.camel@mendozajonas.com> (Samuel Mendoza-Jonas's message of "Tue, 25 Jun 2019 10:38:38 +1000")
>>>>> "Samuel" == Samuel Mendoza-Jonas <sam@mendozajonas.com> writes:
Hi,
>> 2019.02.x is using glibc-2.28. Is using this 2.29-based localedef the
>> right solution for 2019.02.x, or should we be using something 2.28
>> based?
>>
> I've not tested with a localedef ahead of glibc, but if we want to fix up
> 2019.02 as well then basically the same patch minus the 2.28->2.29
> updates should work fine, eg:
> https://github.com/sammj/buildroot/commit/7fedd772a6caac0cbc69a90a8c1da8c142eae9ac
> (not directly tested, but that's the same as what we've been running in our
> 2019.02-based op-build tree)
Great, could you send a patch for 2019.02.x with this?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-06-25 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 2:07 [Buildroot] [PATCH] host-localedef: Compile against glibc-2.29 Samuel Mendoza-Jonas
2019-06-19 11:48 ` Thomas Petazzoni
2019-06-24 18:52 ` Peter Korsgaard
2019-06-25 0:38 ` Samuel Mendoza-Jonas
2019-06-25 6:16 ` Peter Korsgaard [this message]
2019-08-07 7:12 ` Peter Korsgaard
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=87a7e6jijt.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