Include directory not found after installing xtensa compiler
up vote
0
down vote
favorite
I followed these steps to install ESP8266 SDK and Xtensa toolchain separatedly (make STANDALONE=n) on fresh Lubuntu LTS distro. The installation was successfull, I added
$HOME/esp-open-sdk/xtensa-lx106-elf/bin
to PATH directory in .profile and created gccesp script in ~./esp-open-sdk/xtensa-lx106-elf/bin directory to add include and lib path to the compiler:
#!/bin/bash
xtensa-lx106-elf-gcc -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib "$@"
Then I tried to make ~/esp-open-sdk/examples/blinky, with first line of code
#include "ets_sys.h"
The file is located at ~/esp-open-sdk/sdk/include, but the result was
make
gccesp -I. -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib -mlongcalls -c -o blinky.o blinky.c
blinky.c:1:21: fatal error: ets_sys.h: No such file or directory
#include "ets_sys.h"
^
compilation terminated.
So the compiler does not see the include path. Why? I also tried to call the xtensa compiler directly (without the script) but with the same result.
path compiler
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I followed these steps to install ESP8266 SDK and Xtensa toolchain separatedly (make STANDALONE=n) on fresh Lubuntu LTS distro. The installation was successfull, I added
$HOME/esp-open-sdk/xtensa-lx106-elf/bin
to PATH directory in .profile and created gccesp script in ~./esp-open-sdk/xtensa-lx106-elf/bin directory to add include and lib path to the compiler:
#!/bin/bash
xtensa-lx106-elf-gcc -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib "$@"
Then I tried to make ~/esp-open-sdk/examples/blinky, with first line of code
#include "ets_sys.h"
The file is located at ~/esp-open-sdk/sdk/include, but the result was
make
gccesp -I. -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib -mlongcalls -c -o blinky.o blinky.c
blinky.c:1:21: fatal error: ets_sys.h: No such file or directory
#include "ets_sys.h"
^
compilation terminated.
So the compiler does not see the include path. Why? I also tried to call the xtensa compiler directly (without the script) but with the same result.
path compiler
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I followed these steps to install ESP8266 SDK and Xtensa toolchain separatedly (make STANDALONE=n) on fresh Lubuntu LTS distro. The installation was successfull, I added
$HOME/esp-open-sdk/xtensa-lx106-elf/bin
to PATH directory in .profile and created gccesp script in ~./esp-open-sdk/xtensa-lx106-elf/bin directory to add include and lib path to the compiler:
#!/bin/bash
xtensa-lx106-elf-gcc -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib "$@"
Then I tried to make ~/esp-open-sdk/examples/blinky, with first line of code
#include "ets_sys.h"
The file is located at ~/esp-open-sdk/sdk/include, but the result was
make
gccesp -I. -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib -mlongcalls -c -o blinky.o blinky.c
blinky.c:1:21: fatal error: ets_sys.h: No such file or directory
#include "ets_sys.h"
^
compilation terminated.
So the compiler does not see the include path. Why? I also tried to call the xtensa compiler directly (without the script) but with the same result.
path compiler
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I followed these steps to install ESP8266 SDK and Xtensa toolchain separatedly (make STANDALONE=n) on fresh Lubuntu LTS distro. The installation was successfull, I added
$HOME/esp-open-sdk/xtensa-lx106-elf/bin
to PATH directory in .profile and created gccesp script in ~./esp-open-sdk/xtensa-lx106-elf/bin directory to add include and lib path to the compiler:
#!/bin/bash
xtensa-lx106-elf-gcc -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib "$@"
Then I tried to make ~/esp-open-sdk/examples/blinky, with first line of code
#include "ets_sys.h"
The file is located at ~/esp-open-sdk/sdk/include, but the result was
make
gccesp -I. -I~/esp-open-sdk/sdk/include -L~/esp-open-sdk/sdk/lib -mlongcalls -c -o blinky.o blinky.c
blinky.c:1:21: fatal error: ets_sys.h: No such file or directory
#include "ets_sys.h"
^
compilation terminated.
So the compiler does not see the include path. Why? I also tried to call the xtensa compiler directly (without the script) but with the same result.
path compiler
path compiler
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 6 at 21:43
Jan Turoň
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 6 at 21:43
Jan Turoň
1011
asked Dec 6 at 21:43
Jan Turoň
1011
1011
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jan Turoň is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Jan Turoň is a new contributor. Be nice, and check out our Code of Conduct.
Jan Turoň is a new contributor. Be nice, and check out our Code of Conduct.
Jan Turoň is a new contributor. Be nice, and check out our Code of Conduct.
Jan Turoň is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486471%2finclude-directory-not-found-after-installing-xtensa-compiler%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
