From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/tzdata: bump version to 2020f
Date: Mon, 15 Feb 2021 10:12:34 +0100 [thread overview]
Message-ID: <87h7mdbsot.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210214203543.GA2945341@scaer> (Yann E. MORIN's message of "Sun, 14 Feb 2021 21:35:43 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
> So it looks like the duplicated header is causing issues everywhere...
>> I added back the previous default zic format "fat" instead of "slim" [1] to pass
>> the test. The default format has been changed in 2020b release.
>> I'm not sure if we should keep the "fat" format...
>> [1] https://github.com/eggert/tz/commit/6ba6f2117b95eab345a7ed9159cef939e30c4cd3
https://github.com/eggert/tz/commit/7879a3fba1310da0ccc1c336515b5b4a409c3ccb
(the commit adding the slim variant) gives more info.
> To be noted: the glibc version used in thoses tests is 2.18, released in
> August 2013...
> It seems the support for the slim format was only introduced with glibc
> 2.32. 2.31 has no mention of either slim or fat, while 2.32 mention
> both, as it synced with upstream tz 2020a; the previous sync was with
> 2018i...
It is also not clear to me exactly when the slim format support was
added to glibc, but as additional datapoints, I have it working with a
2.30 based toolchain built by 2020.02.x and a 2.31 based one built by
2020.11.x.
> So, what I suggest we do:
> - for master (and next): revert to fat for external glibc, use slim
> for internal glibc (check for c-sky)
> - for maintenance branches: unconditionally revert to fat.
Sounds sensible. Please do it in 2 patches, E.G. first use fat
everywhere, and then as a followup patch change to slim for internal
glibc.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-15 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 16:47 [Buildroot] [PATCH 1/2] package/zic: bump version to 2020f Bernd Kuhls
2021-01-10 16:47 ` [Buildroot] [PATCH 2/2] package/tzdata: " Bernd Kuhls
2021-01-12 17:40 ` Peter Korsgaard
2021-02-14 15:06 ` Romain Naour
2021-02-14 15:30 ` Peter Korsgaard
2021-02-14 15:44 ` Romain Naour
2021-02-14 16:34 ` Peter Korsgaard
2021-02-14 18:21 ` Alexandre Belloni
2021-02-14 18:35 ` Romain Naour
2021-02-14 20:35 ` Yann E. MORIN
2021-02-14 21:32 ` Romain Naour
2021-02-15 0:01 ` Alexandre Belloni
2021-02-15 9:12 ` Peter Korsgaard
2021-02-15 9:12 ` Peter Korsgaard [this message]
2021-02-15 9:34 ` Romain Naour
2021-02-15 11:02 ` Peter Korsgaard
2021-01-10 18:34 ` [Buildroot] [PATCH 1/2] package/zic: " Yann E. MORIN
2021-01-12 17:40 ` 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=87h7mdbsot.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.