/lib64 /lib32 /lib Debian AMD64

Arnaud_B · 05-09-2007, 02:38 AM

Hi,
I noticed that in Debian AMD64 /lib is a symlink to /lib64 and /lib32 is a symlink to /emu/ia32-libs (if I remember well, I don't have the machine with me now...).
I was wondering if there is anything I should know about it in term of administration of the system. Would this mean for instance that I should install 32 bits apps in /lib32?
Sorry if this is an obvious question but I would just like to know what is the good way to work with an AMD64 system :-)
Thanks,
A.

osor · 05-09-2007, 11:58 AM

This is a generic “multilib” setup. If you use your package manager, it should take care of placement of 32-bit libraries to {,/usr}/lib32 and normal libraries to {,/usr}/lib64. When you are compiling yourself, it should already be taken care of as /lib points to /lib64. Only when you want to compile 32-bit libraries will you have to specify the library install prefix explicitly as /usr/lib32 or whatever.

HappyTux · 05-09-2007, 01:12 PM

Quote:

Originally Posted by Arnaud_B

Hi,
I noticed that in Debian AMD64 /lib is a symlink to /lib64 and /lib32 is a symlink to /emu/ia32-libs (if I remember well, I don't have the machine with me now...).
I was wondering if there is anything I should know about it in term of administration of the system. Would this mean for instance that I should install 32 bits apps in /lib32?
Sorry if this is an obvious question but I would just like to know what is the good way to work with an AMD64 system :-)
Thanks,
A.

Debian amd64 is pure 64bit the /emu/ia32-libs directory is there for as the name suggest emulation of the 32bit libs that work using that. If you want to run 32bit apps then you need to setup was is called a chroot install of a 32bit system in addition to your running 64bit system (both will run at the same time), then you run your 32bit apps within this 32bit chroot environment.