On 1/4/20, Alan Feuerbacher <[email protected]> wrote: > On 1/4/2020 12:49 PM, Xi Ruoyao wrote: >> On 2020-01-04 10:21 -0700，Alan Feuerbacher wrote: >>> I've run into a problem in building Version 20200101-systemd Section >>> 6.9. Glibc-2.30. >>> >>> After several repetitions of compiling, I've found that if I run >>> "make check", the various localedef invocations that follow, like >>> "localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8", sometimes fail with a message >>> like >>> "cannot create temporary file: /tools/lib/locale/locale-archive.J6uC5g: >>> No such file or directory". >>> However, if I skip "make check", all of the "localedef" commands >>> run ok. >> That's abnormal. NEVER continue blindly with this kind of phenomena. >> That may >> be a bomb and may blow up your entire system. > > Can you please expand on what I did wrong? I don't really understand > what you mean by "continue blindly".
While you're waiting for the reply, my brain's interpretation is that it is a well-meaning version of "STOP! DO NOT PASS *GO*! DO NOT COLLECT $200!" In a good way, I mean... :) Their advisement further a little bit sounds like whatever's going on in the error maybe could potentially affect your ENTIRE system *including your very important, very necessary HOST operating system*. That would be a reason for advising that everything come to a complete stop until you can figure out what's going on. This is phenomenally coincidental to something I JUST seconds ago typed over at Debian-User. Why they might say STOP NOW, DON'T TOUCH *ANYTHING* until we figure this out is because maybe the error's trying to say that something may be accidentally linked directly into your *HOST* system, not the practice play session. If that is in any way the case, if you were to do something like start deleting everything in your play session, it's possible that... maybe... a "hard link" is pointing at your HOST session. If that is what's going on AND you were to start deleting your PLAY session to go back to Chapter 1 or something, that accidentally created wrong *hard link* WILL delete your *HOST* system files. I'm speaking firsthand from having created exactly that situation during my earliest Debian debootstrap efforts. Actually, I got a HARSH reminder AGAIN in later debootstraps when I deleted a "mount -B link that was pointed at thousands of package archive files. I used to "soft link" a symlink to those same package archive files until debootstrap failed for that very reason so I learned to go the "mount --bind" route. THEN I learned the very hard way that you can harmlessly delete a "soft link" but a mounted "mount -B" link will wipe out that hard link AND the directory it's feeding from.... Heartbreaking doesn't begin to cover learning something like that by being the one who did it firsthand..... A healthy, ACTIVE backup system is a User's best friend in these cases..... Cindy :) -- * runs with an open copy of my own LFS BOOK RIGHT NOW in the next browser tab over! * -- 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
