On 1/28/06, Dan Nicholson <[EMAIL PROTECTED]> wrote: > 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"? > Hmm...
ldd /usr/bin/localedef /tools/bin/ldd: line 124: /usr/bin/localedef: No such file or directory That's really strange O_O readelf -d /usr/bin/localedef Dynamic section at offset 0x50f28 contains 20 entries: Tag Type Name/Value 0x00000001 (NEEDED) Shared library: [libc.so.6] Then 19 other entries, if you really need them I'll type them up, but it's alot. > > > > 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? > 20051217 does not have glibc-libidn, I just noticed that in 2006, but 20051217 does not. The ldd above is chrooted, here is the other one. ldd /tools/bin/localedef linux-gate.so.1 => (0xffffe000) libc.so.6 => /tools/lib/libc.so.6 (0xb7e51000) /tools/lib/ld-linux.so.2 (oxb7f74000) > > > > 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. > Hmm... well it's off of the liveCD, I really don't kow if it's UTF-8 enabled, I know my charset is default "C", I didn't pick UTF-8 or that ISO one. Now that I check, there is a UTF-8 one but it's not what I'm using. However I do know that I built part of this system using the US-ISO standard charset... then I switched to default... was that a bad move? (it was ISO-8859-1 and now I'm using Default/Other... which I don't know what it is really) > 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 > Hope that helps you help... eheh. - Michael -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
