On Mon, May 17, 2010 at 1:44 PM, mike <mikere...@onetel.com> wrote:
> Sorry for the newbie question ...
>
> I need the build process to look for libelf in /usr/lib but gmp, ppl, cloog,
> etc. in /usr/local/lib.  I've tried lots of combinations of the
> flags/options listed by 'configure --help' including this:
>
>> ~/GCC/gcc-4.5.0/configure --program-suffix=-4.5.0
>> --with-libelf-include=/usr/include --with-libelf-lib=/usr/lib
>> --with-mpc=/usr/local/lib --with-mpfr=/usr/local/lib
>> --with-gmp=/usr/local/lib --with-ppl=/usr/local/lib
>> --with-cloog=/usr/local/lib
>
> but what always happens is that when it goes into i686-pc-linux-gnu/libgcc
> in the object directory I get this:
>
>> configure:3233: /home/mike/GCC-obj-dir/./gcc/xgcc
>> -B/home/mike/GCC-obj-dir/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/
>> -B/usr/local/i686-pc-linux-gnu/lib/ -isystem
>> /usr/local/i686-pc-linux-gnu/include -isystem
>> /usr/local/i686-pc-linux-gnu/sys-include    -c -g -O2  conftest.c >&5
>> /home/mike/GCC-obj-dir/./gcc/cc1: error while loading shared libraries:
>> libmpc.so.2: cannot open shared object file: No such file or directory
>> configure:3237: $? = 1
>> configure: failed program was:
>
> and there is this in config.log in the object libgcc directory:
>
>> configure:3020: /home/mike/GCC-obj-dir/./gcc/xgcc
>> -B/home/mike/GCC-obj-dir/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/
>> -B/usr/local/i686-pc-linux-gnu/lib/ -isystem
>> /usr/local/i686-pc-linux-gnu/include -isystem
>> /usr/local/i686-pc-linux-gnu/sys-include    -o conftest -g -O2   conftest.c
>> >&5
>> /home/mike/GCC-obj-dir/./gcc/cc1: error while loading shared libraries:
>> libmpc.so.2: cannot open shared object file: No such file or directory
>> configure:3023: $? = 1
>
> Depending on what flags/options I use with 'configure' it might not find
> libelf.so.0 instead.

This question is more appropriate for gcc-help.

You need to set your LD_LIBRARY_PATH environment to point
to the installed libraries or ensure to configure your ld.so to pick
them up.

Richard.

> Thanks,
> Mike
>
>

Reply via email to