ESP8266 Community Forum

- Mon Sep 18, 2017 7:22 am #70075 Hello,
I am having a problem compiling the source code of the NONOS_SDK under Ubuntu linux.
I tried to compile the blinky example with using the attached makefile and it worked the first time.
I even downloaded it in the ESP8266 and I have the led blinking.
Just to try I changed the number of milliseconds in the example and I tried to recompile it again but I didn't have success.
The error I get is the followig:

Code: Select allfranco@franco-VirtualBox:~/esp-open-sdk/blinky$ make
xtensa-lx106-elf-gcc -I. -mlongcalls   -c -o blinky.o blinky.c
make: xtensa-lx106-elf-gcc: Command not found
<builtin>: recipe for target 'blinky.o' failed
make: *** [blinky.o] Error 127
franco@franco-VirtualBox:~/esp-open-sdk/blinky$


I already put
export PATH="$PATH:~/esp-open-sdk/xtensa-lx106-elf/bin/:~/esp-open-sdk/esptool:~/esp-open-sdk/xtensa-lx106-elf/xtensa-lx106-elf"
In both .profile and .bashrc.
If I try manually to launch the compiler I get an error that it cannot find the libraries but it finds the command.
Why does make not find it?
Is it a known problem (due to my linux-newbbiness) or is it something new?
I think it's something stupid that I am missing but I cannot figure it out myself
I hope you can help me.

- Wed Sep 20, 2017 2:03 am #70133 It took 3 days to be approved... In the meantime I solved.
The problem is in the export PATH...
1) Don't use the ~, put the full path "/home/username/esp-open-sdk/..."
2) $PATH must be at the end and not at the beginning

For bash it doesn't make any difference, manually you can call it from the command line even with the "wrong" path name but apparently for make it makes a difference.
So be careful.
I hope I can contribute with something more substantial in the future, it seems to be a nice forum