Ben Collins <[EMAIL PROTECTED]> writes: > Ok, I've gotten glibc 2.1.1-0.1 compiled. No real problems (atleast no > C++ libs problems like i386 is having).
> Only thing I see wrong is tar broke: > tar: error in loading shared libraries: tar: symbol chown, version > GLIBC_2.1 not defined in file libc.so.6 with link time reference > GLIBC_2.1 is defined (atleast it shows when I grep strings libc.so.6) > in libc. > The `chown' comand works fine, however, and nothing else seems to be > affected. Could this be a bad compile of tar or was the previous glibc > 2.1pre's compiled with some strange symbols? Hmm, it looks like 2.0.105 has a version 2.1 chown: # objdump -T /lib/libc-2.0.105.so | grep chown 00000000000a88a8 g DF .text 00000000000000a4 GLIBC_2.1 chown 00000000000a894c g DF .text 000000000000001c (GLIBC_2.0) chown 00000000000a8968 w DF .text 0000000000000000 GLIBC_2.0 fchown 00000000000a899c w DF .text 0000000000000000 GLIBC_2.0 lchown 00000000000a88a8 g DF .text 00000000000000a4 GLIBC_2.1 __chown But the new one doesn't: # objdump -T libc.so |grep chown 0000000000095008 w DF .text 0000000000000000 GLIBC_2.0 fchown 000000000009503c w DF .text 0000000000000000 GLIBC_2.0 lchown 0000000000094fd4 w DF .text 0000000000000000 GLIBC_2.0 chown Looking at "tar": # objdump -T /bin/tar |grep chown 000000000003f5a0 DF *UND* 00000000000000a4 GLIBC_2.1 chown 000000000003f9fc w DF *UND* 0000000000000000 GLIBC_2.0 lchown And "chown": # objdump -T /bin/chown |grep chown /bin/chown: file format elf32-sparc 0000000000022080 w DF *UND* 0000000000000000 GLIBC_2.0 chown This should explain the error that you are seeing, but it doesn't explain why I don't see the problem on my test machine. Wait - I am seeing the problem with other programs. Steve [EMAIL PROTECTED]