You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When cross compiling GCC while the current directory is in the PATH variable, compilation fails with the error message:
checking for i686-pc-linux-gnu-gcc... (cached) gcc
checking for C compiler default output file name...
configure: error: in `/tmp/dcl9934/cross-tools/build-gcc/gcc':
configure: error: C compiler cannot create executables
See `config.log' for more details.
If you go to compile gcc manually, you'll see a more useful message:
This problem here is that GCC creates a symlink to the 'as' for the target platform, and puts it in the build-gcc/gcc directory. So, when we try to compile something for the host, we end up using the target's 'as' instead!
gcc$ which as
./as
gcc$ as --verbose
GNU assembler version 2.23.1 (arm-none-eabi) using BFD version (GNU Binutils) 2.23.1
Either the user need to remove '.' from their path, or we should remove it from the environment when we build GCC by submake.
The text was updated successfully, but these errors were encountered:
When cross compiling GCC while the current directory is in the PATH variable, compilation fails with the error message:
If you go to compile gcc manually, you'll see a more useful message:
This problem here is that GCC creates a symlink to the 'as' for the target platform, and puts it in the build-gcc/gcc directory. So, when we try to compile something for the host, we end up using the target's 'as' instead!
Either the user need to remove '.' from their path, or we should remove it from the environment when we build GCC by submake.
The text was updated successfully, but these errors were encountered: