Edwin Groothuis fffd993df2 On 64 bit architectures, you can run 32 bit executables and the rtld can trace them, but ldd(1) doesn't know yet how to detect them:
[/] root@ed-exigent>ldd `which httpd`
    ldd: /usr/local/sbin/httpd: can't read program header
    ldd: /usr/local/sbin/httpd: not a dynamic executable

    But...

    [/] root@ed-exigent>LD_32_TRACE_LOADED_OBJECTS==1 `which httpd`
    libm.so.4 => /lib32//libm.so.4 (0x280c8000)
    libaprutil-1.so.2 => /usr/local/lib/libaprutil-1.so.2 (0x280de000)
    libexpat.so.6 => /usr/local/lib/libexpat.so.6 (0x280f2000)
    libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28110000)
    libapr-1.so.2 => /usr/local/lib/libapr-1.so.2 (0x281fd000)
    libcrypt.so.3 => /lib32//libcrypt.so.3 (0x2821d000)
    libpthread.so.2 => not found (0x0)
    libc.so.6 => /lib32//libc.so.6 (0x28235000)
    libpthread.so.2 => /usr/lib32/libpthread.so.2 (0x2830d000)

Added support in ldd(1) for the LD_32_xxx environment variables if
the architecture of the machine is >32 bits. If we ever go to 128
bit architectures this excercise will have to be repeated but thanks
to earlier commits today it will be relative simple.

PR:		bin/124906
Submitted by:	edwin
Approved by:	bde (mentor)
MFC after:	1 week
2008-07-03 22:37:51 +00:00
..
2008-03-03 08:32:58 +00:00
2008-04-04 21:33:41 +00:00
2007-11-09 16:31:47 +00:00
2008-02-05 17:34:44 +00:00
2007-11-30 11:02:36 +00:00
2008-02-19 07:09:19 +00:00
2007-11-07 07:59:38 +00:00
2008-06-08 12:43:02 +00:00
2008-02-09 09:12:02 +00:00
2008-06-17 18:56:04 +00:00
2008-05-19 11:35:11 +00:00
2008-01-16 19:27:43 +00:00
2007-11-07 07:56:57 +00:00
2008-05-16 20:09:29 +00:00
2008-06-30 17:16:05 +00:00
2008-01-15 07:40:30 +00:00
2008-04-04 21:35:13 +00:00
2008-05-13 09:42:03 +00:00