Info regarding the selection of 64-bit vs. 32-bit shared libs

Info regarding the selection of 64-bit vs. 32-bit shared libs

[Anil E. Sahukar]

Hello,

I have found that I am missing some critical information regarding the
executable loading process when shared libs and a 64-bit app are
involved.

Specifically, I have LD_LIBRARY_PATH is set to /usr/lib and /lib.

In one case, 64-bit app A loads the 64-bit version of its shared libs
(including libGL.so) and runs happily.  

In another case, 64-bit app B does not...until LD_LIBRARY_PATH is set to
/lib64 and /usr/lib64.

I'd like to understand why app A loads properly without changing the
LD_LIBRARY_PATH.  

If possible, could you point me to the proper documentation?

Thanks in advance for the help,

AJ Sahukar
asahukar@altair.com

Re: Info regarding the selection of 64-bit vs. 32-bit shared libs

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

On Thursday 06 July 2006 13:03, Anil E. Sahukar wrote:
> I have found that I am missing some critical information regarding the
> executable loading process when shared libs and a 64-bit app are
> involved.

binutils isnt involved in the runtime library loading process ... that is the 
ld.so (usually provided by glibc)

you probably want to try these docs:
http://www.iecc.com/linker/
http://docs.sun.com/app/docs/doc/817-1984
http://www.caldera.com/developers/gabi/
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]