Using a non-standard library path when compiling software

Jeff91 · 01-10-2010, 01:45 AM

I was wondering if there is an argument I can pass to the configuration file to have it use a library from a non-standard path to compile with - for example I would like it to use my perl located in /scratchbox/users/jeff91/usr/bin/perl instead of the standard /usr/bin/perl

Can I do this somehow?

Thanks,
~Jeff

EricTRA · 01-10-2010, 01:55 AM

Hello,

You can find out what options/parameters you can give to a configure script by typing:

Code:

./configure --help

or

Code:

./configure -h

Then look if there is an option like:

Code:

--with-perl=

If the option is not available then you could always create a link to your perl in the directory where your configure script is looking for it.

Kind regards,

Eric

knudfl · 01-13-2010, 05:11 PM

'perl' is searching libraries, modules using info
from the binary 'perl' e.g. /usr/bin/perl .

The best setup is of course a chroot environment
( with all your "arm" files )
http://en.wikipedia.org/wiki/Chroot

But a workaround may work : a temporary rename
of /usr/bin/perl to e.g. /usr/bin/perl-5

With only the binary "arm perl" around,
no disturbing "i386" files should then
be picked up.
.....

GooseYArd · 01-13-2010, 05:17 PM

the easiest way is to just modify the environment slightly before you run configure:

PATH=/scratchbox/users/jeff91/usr/bin/perl:$PATH ./configure --blah

If, as you asked, you wanted to link a library from an unusual path, you can say:

CFLAGS="-I/path/to/your/headers" LDFLAGS="-L/path/to/your/lib" ./configure --blah

an autoconf-generated configure script pays attention to those and several other env variables.