Opened 11 years ago
Closed 11 years ago
#3496 closed task (fixed)
/etc/localtime is no longer created by default
Reported by: | Chris Staub | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.5 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
The Glibc instructions have the "--remove-destination" switch on the command to cp the appropriate timezone file to /etc/localtime, but that file is not created by the Glibc installation anymore, so that switch is not needed.
Attachments (1)
Change History (6)
by , 11 years ago
Attachment: | localtime.patch added |
---|
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Bryan, I think this is a slippery slope. We really don't recommend rebuilding glibc outside of the LFS chroot environment. Inside Chapter 6, we know what we've got and there the switch is not needed. Adding commands for what someone might do later seems to be beyond the scope of LFS.
You might have a point for some other package, but glibc is special.
comment:3 by , 11 years ago
Yeah, I can see your point. Hmm.
I guess I'm just being nostalgic -- this particular use of --remove-destination is where I first learned it existed, and I use it all the time at work (where the build system produces binaries with mode 0555 by default, so if you build something and then copy it to a stable location outside the build tree, then upgrading requires either --remove-destination or remembering to change the mode). And we don't use it anywhere else in the book.
But either way I guess.
comment:5 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
What about when compiling glibc a second time (same version, ICA-style)? The file will be there from the first install. What if something else creates a symlink? (You don't want to overwrite the target of the symlink...)