gcc/newlib: Drop gcc-nostdc dependency #36
Conversation
Only "new" files from PREFIX are packaged so after using gcc-nostdc as a
host package some of the crucial files were ignored. This was the root
cause behind the necessity to install gcc-newlib with gcc-nostdc.
The `${TOOLCHAIN_ARCH}-unknown-elf-gcc` and `${TOOLCHAIN_ARCH}-elf-gcc`
aren't found so these must've been previously installed with gcc-nostdc.
The `-elf-newlib-` prefixed executables are still available. `newlib-` links for executables were created even before and this logic remains untouched.
|
Previously there were such GCCs after installing
I've changed the configured prefix to be the first one as it seems to be the most common, the second one also seems to be quite common but I've never seen the third prefix apart from these Conda toolchains. Should the |
|
The target triplet is explained at https://wiki.osdev.org/Target_Triplet |
|
Basically the issue you are running into is the complicated relationship between the compiler and std library - specially confusing on bare metal systems. |
|
Btw it somewhat makes sense for |
Only "new" files from PREFIX are packaged so after using gcc-nostdc as a
host package some of the crucial files were ignored. This was the root
cause behind the necessity to install gcc-newlib with gcc-nostdc.
The
${TOOLCHAIN_ARCH}-unknown-elf-gccand${TOOLCHAIN_ARCH}-elf-gccaren't found by default so these must've been previously installed with gcc-nostdc.
Inavailability of
${TOOLCHAIN_ARCH}-elf-gccis fixed in the second commit.