Configuring GCC 4.8.1, Unable to find a usable ISL

Discussion:

Ivan Stalev

2014-06-14 19:38:39 UTC

Hello,

I am trying to configure/build GCC 4.8.1 from scratch. I do not have
sudo privileges on the machine, so I am attempting to build/install it
in a local directory. I have successfully built/installed GMP, MPC,
MPFR, and ISL locally. I try to configure like this:

../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-isl-lib=/home/mdl/ids103/install/lib
--with-isl-include=/home/mdl/ids103/install/include/isl
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install

The last few lines of the output are:

checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h... yes
checking for the correct version of mpc.h... yes
checking for the correct version of the gmp/mpfr/mpc libraries... yes
checking for version 0.10 of ISL... no
checking for version 0.11 of ISL... no
configure: error: Unable to find a usable ISL. See config.log for details.

configure:5905: checking for version 0.11 of ISL
configure:5924: gcc -o conftest -g -O2
-I/home/mdl/ids103/install/include/isl
-I/home/mdl/ids103/install/include -I/home/mdl/ids103/install/include
-I/home/mdl/ids103/install/include -L/home/mdl/ids103/install/lib
conftest.c -lisl >&5
configure:5924: $? = 0
configure:5924: ./conftest
./conftest: error while loading shared libraries: libisl.so.10: cannot
open shared object file: No such file or directory

However, libisl.so.10 is indeed in /home/mdl/ids103/install/lib. Why
is it not finding it?

About a month ago, I successfully built the new GCC 4.9.0 the same
way, without having any version of ISL installed. I suppose the
configuration I used did not require it. But now, if I try to build
4.8.1, I get an error 15 minutes into the build from what seems to be
due to not having ISL.

Thanks!

Jonathan Wakely

2014-06-14 19:41:11 UTC

Permalink

Post by Ivan Stalev
Hello,
I am trying to configure/build GCC 4.8.1 from scratch. I do not have
sudo privileges on the machine, so I am attempting to build/install it
in a local directory. I have successfully built/installed GMP, MPC,
../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-isl-lib=/home/mdl/ids103/install/lib
--with-isl-include=/home/mdl/ids103/install/include/isl
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install

See http://gcc.gnu.org/wiki/InstallingGCC for a much easier alternative.

ISL is completely optional, unless you specifically want to use the
Graphite loop optimizations then just don't use any --with-isl options
and you don't need any version of ISL.

Ivan Stalev

2014-06-14 20:07:53 UTC

Permalink

Hi,

Okay, now I configured like this:

../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install

I started the build, and 10 minutes into it, I get this error:

checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/home/mdl/ids103/gcc-4.8.1-build/x86_64-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile

The only errors in config.log seem to be related to ISL, and also these:

gcc: error: unrecognized command line option '-V'
gcc: error: unrecognized command line option '-qversion'
g++: error: unrecognized command line option '-V'
g++: error: unrecognized command line option '-qversion'

Thanks again.

Post by Jonathan Wakely

See http://gcc.gnu.org/wiki/InstallingGCC for a much easier alternative.
ISL is completely optional, unless you specifically want to use the
Graphite loop optimizations then just don't use any --with-isl options
and you don't need any version of ISL.

Jonathan Wakely

2014-06-14 20:12:27 UTC

Permalink

Post by Ivan Stalev
Hi,
../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install
checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
configure: error: cannot compute suffix of object files: cannot compile

Read the link I gave you. It links to the FAQ explaining this error:
https://gcc.gnu.org/wiki/FAQ#configure_suffix

And it also shows a much simpler way to build GCC that avoids this
problem. Stop trying to do it the complicated way.

Ivan Stalev

2014-06-14 21:09:51 UTC

Permalink

Thank you for getting back to me.

I ran ./contrib/download_prerequisites as it states in the FAQ.

I then configured like this:

../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin

I used --prefix because I do not have sudo permissions to install in
default directory. I use --with-ld and --with-as because the default
installed versions are old and the software that I will be compiling
requires newer versions of the binutils.

Unfortunately, I still get the same error.

Post by Jonathan Wakely

https://gcc.gnu.org/wiki/FAQ#configure_suffix
And it also shows a much simpler way to build GCC that avoids this
problem. Stop trying to do it the complicated way.

/jd

2014-06-14 21:16:11 UTC

Permalink

Post by Ivan Stalev
Thank you for getting back to me.
I ran ./contrib/download_prerequisites as it states in the FAQ.
../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
I used --prefix because I do not have sudo permissions to install in
default directory. I use --with-ld and --with-as because the default
installed versions are old and the software that I will be compiling
requires newer versions of the binutils.
Unfortunately, I still get the same error.

Post by Jonathan Wakely

https://gcc.gnu.org/wiki/FAQ#configure_suffix
And it also shows a much simpler way to build GCC that avoids this
problem. Stop trying to do it the complicated way.

Did you forcibly remove the config.cache? Likely you're getting the
same error because of that. The approach you're using (recommended by
Jonathan) definitely works. If you're in doubt, remove the directory
you're trying to build into, but use rm -f, like so:

$ find . -name config.cache -exec rm -f {} \;

That will clear your cache from any previous failed configuration attempts.

John

Ivan Stalev

2014-06-14 21:21:06 UTC

Permalink

Hi,

Yes, I removed everything inside the build directory (rm -r *). I
suppose I will retry again.

Thanks,

Ivan

Post by Jonathan Wakely

Post by Ivan Stalev
Hi,
../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install
checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem
/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem
/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
configure: error: cannot compute suffix of object files: cannot compile

https://gcc.gnu.org/wiki/FAQ#configure_suffix
And it also shows a much simpler way to build GCC that avoids this
problem. Stop trying to do it the complicated way.

Did you forcibly remove the config.cache? Likely you're getting the same
error because of that. The approach you're using (recommended by Jonathan)
definitely works. If you're in doubt, remove the directory you're trying to
$ find . -name config.cache -exec rm -f {} \;
That will clear your cache from any previous failed configuration attempts.
John

Ivan Stalev

2014-06-15 00:06:16 UTC

Permalink

Unfortunately, I keep getting build errors:

g++: unrecognized option '-static-libstdc++'
conftest.cpp:11:2: error: #error -static-libstdc++ not implemented

conftest.c:18: error: 'choke' undeclared (first use in this function)
conftest.c:18: error: (Each undeclared identifier is reported only once
conftest.c:18: error: for each function it appears in.)
conftest.c:18: error: expected ';' before 'me'

Post by Ivan Stalev
Hi,
Yes, I removed everything inside the build directory (rm -r *). I
suppose I will retry again.
Thanks,
Ivan

Post by Jonathan Wakely

Post by Ivan Stalev
Hi,
../gcc-4.8.1/configure --prefix=/home/mdl/ids103/gcc-4.8.1-install
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-clocale=gnu --enable-lto --enable-languages=c,c++,fortran
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
--disable-multilib --with-cloog=/home/mdl/ids103/install
--with-gmp=/home/mdl/ids103/install
--with-mpfr=/home/mdl/ids103/install
--with-mpc=/home/mdl/ids103/install
checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem
/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem
/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
configure: error: cannot compute suffix of object files: cannot compile

https://gcc.gnu.org/wiki/FAQ#configure_suffix
And it also shows a much simpler way to build GCC that avoids this
problem. Stop trying to do it the complicated way.

Did you forcibly remove the config.cache? Likely you're getting the same
error because of that. The approach you're using (recommended by Jonathan)
definitely works. If you're in doubt, remove the directory you're trying to
$ find . -name config.cache -exec rm -f {} \;
That will clear your cache from any previous failed configuration attempts.
John

Jonathan Wakely

2014-06-15 08:51:53 UTC

Permalink

Post by Ivan Stalev
g++: unrecognized option '-static-libstdc++'
conftest.cpp:11:2: error: #error -static-libstdc++ not implemented
conftest.c:18: error: 'choke' undeclared (first use in this function)
conftest.c:18: error: (Each undeclared identifier is reported only once
conftest.c:18: error: for each function it appears in.)
conftest.c:18: error: expected ';' before 'me'

That doesn't look like a build error, that looks like a configure test
to find out what is supported - many of those tests are supposed to
fail.

GCC 4.8.1 builds fine on x86_64-unknown-linux-gnu so you must be doing
something wrong, but you're not showing enough information for anyone
to diagnose it.

Ivan Stalev

2014-06-15 16:47:20 UTC

Permalink

Hi,

Yes, those errors are from the configuration step.

Here are the steps I took after untarring the source code:

1) Run this inside the source directory: ./contrib/download_prerequisites
2) Run configure from an empty build directory: ../gcc-4.8.1/configure
--prefix=/home/mdl/ids103/gcc-4.8.1-install
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
3) Run make

After about 20 minutes, the build fails. Here is the last of the output:

rm gcc.pod
make[3]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build/gcc'
mkdir -p -- x86_64-unknown-linux-gnu/libgcc
Checking multilib configuration for libgcc...
Configuring stage 1 in x86_64-unknown-linux-gnu/libgcc
configure: creating cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking for x86_64-unknown-linux-gnu-ar... ar
checking for x86_64-unknown-linux-gnu-lipo... lipo
checking for x86_64-unknown-linux-gnu-nm...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/nm
checking for x86_64-unknown-linux-gnu-ranlib... ranlib
checking for x86_64-unknown-linux-gnu-strip... strip
checking whether ln -s works... yes
checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/home/mdl/ids103/gcc-4.8.1-build/x86_64-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build'
make: *** [all] Error 2

The config.log has not been written to since the configuration step.
Please let me know if I can provide more information.

Thank you.

Post by Jonathan Wakely

That doesn't look like a build error, that looks like a configure test
to find out what is supported - many of those tests are supposed to
fail.
GCC 4.8.1 builds fine on x86_64-unknown-linux-gnu so you must be doing
something wrong, but you're not showing enough information for anyone
to diagnose it.

Jonathan Wakely

2014-06-16 07:13:38 UTC

Permalink

Post by Ivan Stalev
Hi,
Yes, those errors are from the configuration step.
1) Run this inside the source directory: ./contrib/download_prerequisites
2) Run configure from an empty build directory: ../gcc-4.8.1/configure
--prefix=/home/mdl/ids103/gcc-4.8.1-install
--with-ld=/home/mdl/ids103/binutils-2.24-install/bin
--with-as=/home/mdl/ids103/binutils-2.24-install/bin
3) Run make
rm gcc.pod
make[3]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build/gcc'
mkdir -p -- x86_64-unknown-linux-gnu/libgcc
Checking multilib configuration for libgcc...
Configuring stage 1 in x86_64-unknown-linux-gnu/libgcc
configure: creating cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking for x86_64-unknown-linux-gnu-ar... ar
checking for x86_64-unknown-linux-gnu-lipo... lipo
checking for x86_64-unknown-linux-gnu-nm...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/nm
checking for x86_64-unknown-linux-gnu-ranlib... ranlib
checking for x86_64-unknown-linux-gnu-strip... strip
checking whether ln -s works... yes
checking for x86_64-unknown-linux-gnu-gcc...
/home/mdl/ids103/gcc-4.8.1-build/./gcc/xgcc
-B/home/mdl/ids103/gcc-4.8.1-build/./gcc/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/bin/
-B/home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/lib/
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/include
-isystem /home/mdl/ids103/gcc-4.8.1-install/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[2]: *** [configure-stage1-target-libgcc] Error 1
make[2]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/mdl/ids103/gcc-4.8.1-build'
make: *** [all] Error 2
The config.log has not been written to since the configuration step.

I don't think that's true, look for it in the
x86_64-unknown-linux-gnu/libgcc directory.

Please read https://gcc.gnu.org/wiki/FAQ#configure_suffix (which was
linked to from the other wiki page I suggested).

Ivan Stalev

2014-06-16 17:31:49 UTC

Permalink

You are correct. I was looking at the wrong config.log. The problem
ended up being with my --with-as and --with-ld options. I only
specified the directory they are in, as opposed to also including the
binary name. I finally built successfully. I appreciate your help and
patience!

Post by Jonathan Wakely

I don't think that's true, look for it in the
x86_64-unknown-linux-gnu/libgcc directory.
Please read https://gcc.gnu.org/wiki/FAQ#configure_suffix (which was
linked to from the other wiki page I suggested).