On 11/04/2017 10:00, Thomas Seeling wrote:
Hallo,
I've tried jhalfs in the latest 2.4 version and it works quite nicely
for me (used it some years ago to build 6.something).
However it failed for me during 076-glibc today because I made a dumb
mistake. I entered a bad timezone name which I only later realized would
not work because there's no corresponding file in the timezone
repository. I used "CET-1" instead of Europe/Berlin (for me in Germany).
This is wrong even more because we have DST in effect for 2 weeks now ;)
May I suggest to add a sanity check that the desired timezone is a valid
name and exists in /usr/share/zoneinfo?
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.
I hope you have not thought you should start again a whole build, just
because of that error: just change the time zone in the script at
$LFS/jhalfs/lfs-commands/chapter06/076-glibc. Note that doing so will
rebuild glibc and run the tests again. There are several possibilities
to avoid that, but I do not recommend them, unless you have a slow computer.
Pierre
--
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
