Bug#180119: libc6: ld.so does not seem to find correct platform information for AMD K6-III
At Fri, 07 Feb 2003 12:18:24 +0000,
Steve Haslam wrote:
> With libc6 2.3.1-10, ld.so would try to link in the i686/cmov version of
> libssl on a K6-III (i586) machine-- I had to divert the libs away, and it
> then loaded the i586 versions.
>
> Now with 2.3.1-11, ld.so is not loading *any* arch-specific library, and
> using the standard /usr/lib/libssl. Although this is safer, it would be nice
> if the K6-III was recognised.
>
> Here is the output with LD_AUXV=1 set:
>
> bash# LD_SHOW_AUXV=1 LD_DEBUG=libs LD_TRACE_LOADED_OBJECTS=1 LD_BIND_NOW=1
> /usr/bin/openssl version
> AT_HWCAP: fpu vme de pse tsc msr mce cx8 pge mmx
> AT_PAGESZ: 4096
> AT_CLKTCK: 100
> AT_PHDR: 0x8048034
> AT_PHENT: 32
> AT_PHNUM: 6
> AT_BASE: 0x4b196000
> AT_FLAGS: 0x0
> AT_ENTRY: 0x80542c0
> AT_UID: 0
> AT_EUID: 0
> AT_GID: 0
> AT_EGID: 0
> AT_PLATFORM:
> 01811: find library=libssl.so.0.9.7; searching
> 01811: search cache=/etc/ld.so.cache
> 01811: trying file=/usr/lib/libssl.so.0.9.7
> 01811:
> 01811: find library=libcrypto.so.0.9.7; searching
> 01811: search cache=/etc/ld.so.cache
> 01811: trying file=/usr/lib/libcrypto.so.0.9.7
> 01811:
> ...
>
> Presumably the problem is that "AT_PLATFORM" is blank? (Is this a libc6
> problem or kernel problem?)
AT_PLATFORM should contain a valid architecture name. I guess it's
kernel problem, please upgrade your kernel into 2.4.20. I tested on
K5 or K6 machine, but IIRC my test worked well.
> /proc/cpuinfo on that machine:
>
> bash# cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 5
> model : 9
> model name : AMD-K6(tm) 3D+ Processor
> stepping : 1
> cpu MHz : 451.033
> cache size : 256 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 1
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow
> k6_mtrr
> bogomips : 901.12
>
> And uname -m returns "i586".
'uname -m' uses uname() system call, so you may know that it uses
something different mechanism to get platform variable.
Regards,
-- gotom
Reply to: