Build fails, Dell XPS13, Ubuntu 16.04, on newlib about riscv-tools HOT 6 CLOSED

Build output will be easier to read in a

```
verbatim block
```

from riscv-tools.

Doesn't seem like a RISC-V problem. Have you successfully built an x86 toolchain on this machine?

from riscv-tools.

I need to understand some terminology here. When you say 'built an x86 toolchain' in this context, do you mean building a compiler targetting any platform, to operate on x86 (i.e. a cross-compiler such as e.g. one that compiles ARM-native applications on an x86 machine), or a native compiler to build applications for the machine also doing the compilation (x86 target on Ubuntu)?

I've built several cross-compiler without problems. I also have a working toolchain for native x86 compilation in Ubuntu, although I believe this would not use the 'unknown' target.

However I should note that my level of knowledge about the gcc build is not nearly at the level that would enable me to speculate on what the problem related to in any direct way. So regardless of where the problem may lie I am going to need more concrete direction if I am to have any chance of fixing it in meaningful time.

from riscv-tools.

I should've more generically asked "have you built any GCC on this machine".

To isolate RISC-V-specific stuff, I'd try building a native gcc with this exact version of gcc. You can try something like mkdir test-native && cd test-native && ../riscv-gcc/configure --disable-multilib --prefix=/tmp && make from within riscv-gnu-toolchain. Whether that succeeds or fails will give us more information.

from riscv-tools.

Yes, the build succeeded without problems. Making a guess, I suspect this may be related to the fact that the makefile produced gives: host=x86_64-pc-linux-gnu and likewise for target. So it's not trying to build x86_64-unknown-linux-gnu targets. However this is speculation on my part.

from riscv-tools.

An error like this can occur if you run configure or make in the riscv-gcc/gcc subdir instead of in the riscv-gcc dir. However, this should not have happened if using the build scripts.

It isn't clear how to reproduce. The provided info only contains the stderr from the build. Most of the info is in the riscv-gnu-toolchain/build/build.log file which was not provided.

Given the length of time this has been open, and the fact that there have been so many source and script file changes since then, I don't think it serves any purpose to keep this open any longer.

from riscv-tools.