You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No unresolved symbols after linking the firmware ELF.
Firmware build should fail if there are unresolved symbols.
Initially observed by @dnc40085 over in #1755. Historically esptool.py has bailed out if there are undefined symbols, but clearly the current version we have in our tree does not.
I have no idea why this wasn't failing horribly for @pjsg during testing...
Actual behavior
../tools/esptool.py elf2image --flash_mode dio --flash_freq 40m .output/eagle/debug/image/eagle.app.v6.out -o ../bin/
esptool.py v1.2-dev
Warning: ELF binary has undefined symbol calloc
Warning: ELF binary has undefined symbol free
Test code
Include the SJSON module in the build.
NodeMCU version
Which branch are you on? If you know the Git revision then add it here as well. dev
Hardware
n/a
The text was updated successfully, but these errors were encountered:
So it seems none of the functions which use calloc/free aren't actually used by the Lua module, and thus haven't caused actual problems. Now to work out why those functions are even included in the ELF after the linking...
Expected behavior
Initially observed by @dnc40085 over in #1755. Historically
esptool.py
has bailed out if there are undefined symbols, but clearly the current version we have in our tree does not.I have no idea why this wasn't failing horribly for @pjsg during testing...
Actual behavior
Test code
Include the SJSON module in the build.
NodeMCU version
Which branch are you on? If you know the Git revision then add it here as well.
dev
Hardware
n/a
The text was updated successfully, but these errors were encountered: