esp8266 / esp8266-wiki

1.75k stars 298 forks source link

make[1]: xtensa-lx106-elf-gcc: Command not found #26

Open SpaceTeddy opened 9 years ago

SpaceTeddy commented 9 years ago

followed your wiki instruction almost 1:1. the only change is that I used the 0.9.5 SDK

compiling the IoT Demo failed always with the above error. how can I fix it. I use Ubuntu 14.04.1 in Fusion VM. thx

khalilst commented 8 years ago

You need to clone the git repository esp-open-sdk.

git clone --recursive https://github.com/pfalcon/esp-open-sdk make STANDALONE=y |& tee make0.log export PATH="$HOME/esp-open-sdk/xtensa-lx106-elf/bin/:$PATH" alias xgcc="xtensa-lx106-elf-gcc"

See more detailed information at below link. http://www.esp8266.com/wiki/doku.php?id=toolchain

mano1979 commented 7 years ago

in my case, i cannot compile the sdk either.

markh2016 commented 6 years ago

There are three videos showing you how to set this up I made yesterday owing to problems with git hub repositories ,,, bad files that are downloaded and causing this not to compile

These are on my Facebook home page

Please see the following and there after you shouldn't, touch wood have any further problems , fingers crossed

Hope this helps as I also had extreme problems getting this to even compile as of yesterday I spent some three hours and more finding the answers although there are are others with similar bad experiences with this how ever I did manage to solve this thanks to some useful informations on the net and not as described here

You might like to view this yourselves

Here is the address for you ( if you follow this I think you will have at least some success )

https://www.facebook.com/mark.harrington.142892/videos/2091296477783030/?t=0 https://www.facebook.com/mark.harrington.142892/videos/2091321701113841/?t=28 https://www.facebook.com/mark.harrington.142892/videos/2091378541108157/?t=0

eezhijun commented 4 years ago

I encountered the same problem, and I solved it as follows. First, you can refer to the solution provided by espressif. I was caused by the lack of msys32 installation. After the installation was successful, the above problems were successfully solved.