- Wed Apr 01, 2015 12:14 pm
#13198
Change -O2 flag for -Os
- Wed Apr 01, 2015 1:24 pm
#13209
Tried it, still too large. BTW, there are several occations of the -O flag in the Makefile. The gcc calls have no less than 3 -O flags...
- Wed Apr 01, 2015 5:29 pm
#13227
If you're trying to compile the latest nodemcu-firmware branch with the CHERTS dev setup, I had to comment out the "LUA_USE_BUILTIN_MATH" definition in user_modules.h to get past this build error.
I also had to install the latest Python2 version since the CHERTS setup didn't mention it even though it appears to be required to build the newer versions of nodemcu.
Hope this helps.
Markus Gritsch wrote:Tried it, still too large. BTW, there are several occations of the -O flag in the Makefile. The gcc calls have no less than 3 -O flags...
If you're trying to compile the latest nodemcu-firmware branch with the CHERTS dev setup, I had to comment out the "LUA_USE_BUILTIN_MATH" definition in user_modules.h to get past this build error.
I also had to install the latest Python2 version since the CHERTS setup didn't mention it even though it appears to be required to build the newer versions of nodemcu.
Hope this helps.
- Fri Apr 03, 2015 2:08 pm
#13396
Yes, this works, thanks. However I would rather compile an unmodified NodeMCU tree and get the toolchain fixed.
Any idea how the toolchain shipping with the Arduino IDE (maybe the same as CHERTS?) differs from the one used to compile NodeMCU on Linux? (https://travis-ci.org/nodemcu/nodemcu-firmware)
bhasden wrote:If you're trying to compile the latest nodemcu-firmware branch with the CHERTS dev setup, I had to comment out the "LUA_USE_BUILTIN_MATH" definition in user_modules.h to get past this build error.
Yes, this works, thanks. However I would rather compile an unmodified NodeMCU tree and get the toolchain fixed.
Any idea how the toolchain shipping with the Arduino IDE (maybe the same as CHERTS?) differs from the one used to compile NodeMCU on Linux? (https://travis-ci.org/nodemcu/nodemcu-firmware)
