gcc-8-20180225: recipe for target 'configure-target-libbacktrace' failed

[Siegmar Gross]

Hi Thomas,

I cloned nvptx* again and now I was able to build everything.
The new compiler works for my small accelerator programs.

Thank you very much for your help

Siegmar


Am 26.02.2018 um 10:57 schrieb Thomas Schwinge:
> Hi!
> 
> On Mon, 26 Feb 2018 07:58:17 +0100, Siegmar Gross <siegmar.gross@informatik.hs-fulda.de> wrote:
>> ../gcc-8.0.0/configure --prefix=/usr/local/gcc-8.0.0 \
>>     --target=nvptx-none \
>>     --enable-as-accelerator-for=x86_64-pc-linux-gnu \
>>     [...]
> 
>> checking for C compiler default output file name...
>> configure: error: in `/export2/src/gcc-8.0.0/gcc-8.0.0_build/nvptx-none/libbacktrace':
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details.
>> Makefile:11774: recipe for target 'configure-target-libbacktrace' failed
>> make[1]: *** [configure-target-libbacktrace] Error 1
>> make[1]: Leaving directory '/export2/src/gcc-8.0.0/gcc-8.0.0_build'
> 
>> configure:2659: checking for nvptx-none-gcc
>> configure:2686: result: /export2/src/gcc-8.0.0/gcc-8.0.0_build/./gcc/xgcc -B/export2/src/gcc-8.0.0/gcc-8.0.0_build/./gcc/ -B/usr/local/gcc-8.0.0/nvptx-none/bin/ -B/usr/local/gcc-8.0.0/nvptx-none/lib/ -isystem /usr/local/gcc-8.0.0/nvptx-none/include -isystem /usr/local/gcc-8.0.0/nvptx-none/sys-include
> 
>  From a quick look, this is missing the "-B" etc. flags for newlib, which
> would explain:
> 
>> configure:2995: checking for C compiler default output file name
>> configure:3017: /export2/src/gcc-8.0.0/gcc-8.0.0_build/./gcc/xgcc -B/export2/src/gcc-8.0.0/gcc-8.0.0_build/./gcc/ -B/usr/local/gcc-8.0.0/nvptx-none/bin/ -B/usr/local/gcc-8.0.0/nvptx-none/lib/ -isystem /usr/local/gcc-8.0.0/nvptx-none/include -isystem /usr/local/gcc-8.0.0/nvptx-none/sys-include    -g -O2   conftest.c  >&5
>> error opening libc.a
>> collect2: error: ld returned 1 exit status
> 
> ... this error.
> 
> Can you please verify that newlib has been "git clone"d properly, been
> linked into your GCC source tree, and in your GCC build log verify that
> it indeed has been built without errors?
> 
> 
> Grüße
>   Thomas