Open bensuperpc opened 3 years ago
Libbacktrace is for exception handling in CXX but should be Working because it's a GCC buildin. Can you upload the config.log from libbacktrace
.build/aarch64-unknown-elf/build/build-cc-gcc-final/aarch64-unknown-elf/libbacktrace/config.log
Hi! I know this issue is old, but I'm facing the same here, building a cross-compiler for cortex-m0+ (arm-none-eabi).
Note that having the folders in /usr/local/src/...
is normally not a problem since I chown
ed it for me.
Ask me if you need more info or files in order to reason about this issue.
I've been trying to fix the issue searching on the web for more data, and as per this conversation, it seems like building GCC with Fortran support may cause the issue. I'm currently building my toolchain without Fortran support, so I'll tell you what I managed to build successfully and what not.
My brand new C and C++ compilers are well-working for now, so I guess Fortran compiler was indeed the heart of this issue (the original writer of it was also requesting Fortran support, and had exactly the same error message). Should I open a separate issue ?
Probably better to open a issue upstream or see if it is already know or fixed.
I would like to make ARMv8 bare metal toolchain, I tried several configurations, but I still have the same error:
Config: config.txt
Size truncated due to file size (16 MB): build_part1.log build_part2.log
crosstool-NG version: commit: aa98a2e2f3f6f91ab02b932162da4bb60f61c9ba I use docker container with debian 10 buster image
With C only it works, but with CXX it makes this error