On 1/28/06, Michael Chrostowski <[EMAIL PROTECTED]> wrote: > > bash: /usr/bin/localedef: No such file or directory.
Could you do "ldd /usr/bin/localedef" and "readelf -d /usr/bin/localedef"? > > Which really to me seems like a message /usr/bin/localedef is > returning (since it does exist) yet it says bash at the prompt as if > it's bash reporting some issue. I'm pretty sure it has nothing to do with localedef, and more to do with the toolchain. > > However upon entering the chroot environment $LFS/tools/bin/localedef > works properly and $LFS/usr/bin/localedef returns the error message. > When I say $LFS in the chroot environment I mean / but I'll say $LFS > just so you know which part of my HDD I'm talking about. Right. I think I have an inkling what the problem is. You say this is SVN-20051217? Do the glibc instructions tell you to unpack the glibc-libidn tarball? Could you do both "ldd /tools/bin/localedef" and "ldd /usr/bin/localedef" from inside the chroot? > > Any ideas? anyone? please? I thought maybe it's a segfault that isn't > coming out right or something (thus the bash: prompt)... however > compiling without my optimization settings (-O3 -march=penium-m) > doesn't seem to help and all the other tools seem to work properly. Nothing to do with segfaults or optimization. You may have stumbled on a new bug that will not allow us to run localedef in that location. Could you please return the results of the commands above and let me know if this is the UTF-8 enabled book? I don't have access to 20051217, but I think that has the UTF-8 support. Sorry for the hangup, but that's what happens when you build the development book :) -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
