Thanks for your quick respond Jonathan. This is the -extended- output from the make.log file: checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... yes checking if /....../gcc/gcc-5.2.0-work/./gcc/xgcc -B/....../gcc/gcc-5.2.0-work/./gcc/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/bin/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/lib/ -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/include -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/sys-include supports -c -o file.o... yes checking if /....../gcc/gcc-5.2.0-work/./gcc/xgcc -B/....../gcc/gcc-5.2.0-work/./gcc/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/bin/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/lib/ -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/include -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/sys-include supports -c -o file.o... (cached) yes checking whether the /....../gcc/gcc-5.2.0-work/./gcc/xgcc -B/....../gcc/gcc-5.2.0-work/./gcc/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/bin/ -B/....../compilers/gcc-5.2.0/powerpc64-bgq-linux/lib/ -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/include -isystem /....../compilers/gcc-5.2.0/powerpc64-bgq-linux/sys-include linker (/....../gcc/gcc-5.2.0-work/./gcc/collect-ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... make[1]: Leaving directory `/....../gcc/gcc-5.2.0-work' Last few lines are not any different than the part I posted in my very first email. Again, what script does is briefly running 1- cd gcc-VERSION-work 2- gcc-VERSION/configure $configars 3- make 4- make install In addition to make.log, this is the last 30 lines of configure.log: checking for powerpc64-bgq-linux-readelf... powerpc64-bgq-linux-readelf checking for strip... no checking for powerpc64-bgq-linux-strip... powerpc64-bgq-linux-strip checking for windres... no checking for powerpc64-bgq-linux-windres... no checking for windmc... no checking for powerpc64-bgq-linux-windmc... no checking where to find the target ar... pre-installed checking where to find the target as... pre-installed checking where to find the target cc... just compiled checking where to find the target c++... just compiled checking where to find the target c++ for libstdc++... just compiled checking where to find the target dlltool... pre-installed checking where to find the target gcc... just compiled checking where to find the target gcj... pre-installed checking where to find the target gfortran... just compiled checking where to find the target gccgo... pre-installed checking where to find the target ld... pre-installed checking where to find the target lipo... pre-installed checking where to find the target nm... pre-installed checking where to find the target objcopy... pre-installed checking where to find the target objdump... pre-installed checking where to find the target ranlib... pre-installed checking where to find the target readelf... pre-installed checking where to find the target strip... pre-installed checking where to find the target windres... pre-installed checking where to find the target windmc... pre-installed checking whether to enable maintainer-specific portions of Makefiles... no configure: creating ./config.status config.status: creating Makefile On Thu, Feb 22, 2018 at 11:04 AM, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: > On 22 February 2018 at 15:55, Fatih Ertinaz wrote: >> One quick question: >>>> --target=powerpc64-bgq-linux \ >>>> --host=powerpc64-linux-gnu \ >>>> --build=powerpc64-linux-gnu \ >>> >>> Those host and build values look wrong. >> Why? > > Because "powerpc64-linux-gnu" looks like a triplet with cpu=powerpc64 > (which is OK) and vendor=linux (which is wrong) and os=gnu (which is > wrong). > > >>> We don't know what your script does so can't really help. >> The script is quite long however it is doing something very simple at its core: >> It creates the gcc-VERSION-work directory and calls configure with the >> options from the gcc-VERSION/ as it is suggested in the documentation. >> It then runs make & make install. >> >> This is the list of libraries found in gcc-5.2.0-work/powerpc64-bgq-linux/ >> libatomic libgcc libgomp libquadmath libssp >> >> So my question is, what makes those ones compiled but not libstdc++-v3? > > Well it comes after them alphabetically, so maybe it hasn't got there yet. > > You have all the logs and 'make' output, and we have none of it, so > only you can see why it fails. Simply showing us the last few lines > doesn't show any errors.
