howto tell "make install" look in /usr/lib64 instead of in /usr/lib?

tramni1980 · 06-01-2012, 03:22 PM

Hello,
I am compiling a package and have some trouble at the "make install" phase.
"make install" searches for libexpat.so in /usr/lib, instead of /usr/lib64. This is troublesome as I am compiling on a multilib system. Making symbolic links to the respective file in /usr/lib64 eliminates the error. Have you got an idea how I can tell "make install" to look for libexpat.so in /usr/lib64 instead of in /usr/lib?
Maybe this is some environmental variable but I do no know which. Any suggestions will be appreciated.

Ser Olmy · 06-01-2012, 03:43 PM

Usually, make install doesn't look for anything, anywhere; it just copies files (executables, libraries, config files and documentation) into the relevant directories. Plain make does the actual compiling and may need to locate various libraries.

The location of libraries is specified in the Makefile, which in turn is usually generated by ./configure. The latter can take a number of arguments and parameters. Run ./configure --help, and you'll probably find that the --libdir argument lets you specify the library directory. There may also be an argument specific to libexpat.

ponce · 06-01-2012, 03:51 PM

If I have understod what you mean, you are having problems with the linker: to have it look into /usr/lib64 you have to pass an LDFLAGS variable to the configure.

have a look at faq 18 on slackbuilds.org.

TracyTiger · 06-01-2012, 09:08 PM

I'm new to mulitilib but my understanding is that if you want the 64bit libraries then you do NOT run in the environment set up by /etc/profile.d/32dev.sh. That is, do NOT run this script in the shell where you make your program. Just let it use the 64bit libraries.

Perhaps you're running in the 32bit preferred environment set by this script ???

This has worked for me the few times I tried it. In my cases I didn't have to explicitly set any environmental path variables.

... but remember I'm new to the multilib setup ...