These would be the directories /lib32, /lib64, etc. Purpose: There may be one or more variants of the /lib directory on systems which support more than one binary format requiring separate libraries. This is commonly used for 64-bit or 32-bit support on systems which support multiple binary formats, but require libraries of the same name.

In this case, /lib32 and /lib64 might be the library directories, and /lib a symlink to one of them. On my Slackware 14.2 for example there are /lib and /lib64 directories for 32-bit and 64-bit libraries respectively even though /lib is not as a symlink as the FHS snippet would suggest:

2011年9月20日 · Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special featur

2023年6月21日 · Whether libraries get put into the lib or lib64 subdirectory therefore depends on the individual project and there is no hard rule for predicting the directory layout from the outside. The exact directory structure within the install directory is determined by the INSTALL commands given to CMake, in particular the DESTINATION field.

2012年9月14日 · lib64 is defined in gcc/config/i386/t-linux when GCC is compiled. The version of GCC that comes with the ...

2012年7月7日 · Some newer applications might be looking in /usr/lib64 for libraries, while some legacy code might be using /usr/lib. Other distributions can provide multi-architecture support, having 32 bit and 64 bit libraries installed on the same machine, which would then be placed in /usr/lib and /usr/lib64 accordingly.

2012年1月4日 · Among other things, this involves moving arch-specific libraries into /usr/lib/<triplet>, dropping the limitations of lib32 and lib64 (where will the new x32 ABI go? where do qemulated binaries live? etc.) as well as extending the package manager to handle mixed-architecture installations much more sanely.

2017年1月10日 · Update: for the time being I can work around the issue by symlinking everything under lib64 into lib. Obviously, that is not an ideal solution; at the very least it defeats the purpose of introducing lib64 (being able to have 32 and 64 bit versions side-by-side) in the first place. I'd much prefer something in a config file.

2013年5月19日 · If you start installing more stuff into /usr/local/lib64, currently-working applications may suddenly break in unpredictable fashion. Share Follow

2017年10月26日 · Recently, I have learned a trick that if a file lacks executable permissions, we can run that file by using /lib64/ld-linux-x86-64.so.2. For example, to restore x permission for -rw-r--r-- 1 root root 59K Mar 1 2017 /bin/chmod