|
Re: Problem accessing gcc [message #1836310 is a reply to message #1836301] |
Mon, 28 December 2020 21:42 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
Eclipse didn't add the /sh -- make did.
It's the default shell used by make
and it can't find arm-none-eabi-gcc
Here's an exampleInvoking: GCC C++ Compiler
g++-bad -std=c++17 -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"src/TestIncludes.d" -MT"src/TestIncludes.o" -o "src/TestIncludes.o" "../src/TestIncludes.cpp"
/bin/sh: g++-bad: command not found
make: *** [src/subdir.mk:20: src/TestIncludes.o] Error 127
You should avoid using relative paths for things like compilers.
The path will be relative to the current directory when running make.
It may not be what you expect.
Try setting the compiler command path in the Cross Compile settings if you are using an Eclipse Managed Build. Otherwise, fix your makefile.
[Updated on: Mon, 28 December 2020 22:06] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.03782 seconds