On 9/5/06, Matthias B. <[EMAIL PROTECTED]> wrote:
[snip]
If you've followed the advice from the hint you should have logged your glibc installation. This is an excerpt from my install.log make[2]: Entering directory `/usr/src/glibc/builddir/glibc-2.4/po' msgfmt -o be.mo be.po .././scripts/mkinstalldirs /usr/share/locale/be/LC_MESSAGES mkdir /usr/share/locale/be *** mkdir /usr/share/locale/be mkdir /usr/share/locale/be/LC_MESSAGES *** mkdir /usr/share/locale/be/LC_MESSAGES As you can clearly see, glibc calls mkdir with full path. Grep your LOG for LC_MESSAGES and post the surrounding text.
Thanks for your explanation Matthias. I'm going to do soon a fresh LFS (and BLFS) install using package users. When and if I find a similar situation, I will check the log to see what is the command that is responsible. --Luca -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
