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! On Mon, Jun 16, 2014 at 3:13 AM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: > On 15 June 2014 17:47, Ivan Stalev wrote: >> 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. > > 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).
