Kuba wrote:
On Tue, 11 Apr 2017 10:33:43 +0200, Pierre Labastie
<[email protected]> wrote:
On 11/04/2017 10:00, Thomas Seeling wrote:
That could be done, but what would it bring? The host
/usr/share/zoneinfo should not be used, unless one can assert it is
the same as the one in the to-be-built glibc. I guess it is usually
the case, but who knows what distros may do? So it can only be checked
after glibc has been installed, and fail there, which is roughly
equivalent to what happened to you.
It is possible to do the check early. First, extract only the
glibc-VERSION/timezone folder from the sources. Then
grep "^Zone\s*TIMEZONE\s" path/to/glibc-VERSION/timezone/* 2>/dev/null
| wc -l
gives 1 for correct timezones and 0 for the incorrect ones.
For jhalfs this is more effort than it is worth. There is no guarantee
that the glibc tarball even exists on the system when jhalfs is run.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
