Latest master with ESP-IDF v4.1 - ldgen fails to create esp-idf/esp32/ld/esp32.project.ld

[atanisoft]

Latest master with ESP-IDF v4.1 - ldgen fails to create esp-idf/esp32/ld/esp32.project.ld

[TrainzLuvr]

That did it, my sdkconfig still had ...=y

Compiled to completion now. Thanks!

[atanisoft]

Yeah, this one is a nasty one, I worked around it locally in generation.py to avoid the None case. I'll submit a PR to upstream to fix it.

[TrainzLuvr]

Sorry to re-open this but the error still persist. I pulled the latest master few minutes ago.

Running ESP-IDF v4.1.

[atanisoft]

Did you remove the sdkconfig file? If not you will need to comment out CONFIG_LWIP_IRAM_OPTIMIZATION which is disabled here.

[karlp]

I'm still getting this on 4.2 release, with LWIP_IRAM_OPTIMIZATION unchecked in menuconfig?

[atanisoft]

I'm still getting this on 4.2 release, with LWIP_IRAM_OPTIMIZATION unchecked in menuconfig?

@karlp Can you send me your sdkconfig and I'll compare it to the one I'm using and see if I can find which option is causing the issue.

[karlp]

Sure, I've attached it here. I suspect it might be wonky toolchains though. I get this if I run cmake directly inside netbeans, from a plain project (no prior build, ie akin to a clean checkout of the project from git)

If I run "idf.py build" once, it works, so... "unsupported tooling" I guess?
sdkconfig.txt

also.... I'm sorry, I missed that I wason't on the repo I thought I was on, so this isn't really your issue at all, I just got here from a bug report on esp-idf, sorry!

[atanisoft]

also.... I'm sorry, I missed that I wason't on the repo I thought I was on, so this isn't really your issue at all, I just got here from a bug report on esp-idf, sorry!

No worries. Try disabling the following options:

CONFIG_ESP32_WIFI_IRAM_OPT=y
CONFIG_ESP32_WIFI_RX_IRAM_OPT=y

[karlp]

hrm, that didn't help, but it still works with "idf.py build" so something's going odd with how cmake runs from inside netbeans. Once it's built once, even a clean/build with netbeans works.

thanks for looking at this, but i'm not going to follow it up further at this point, building once from the commandline is ok for me rightnow.

[atanisoft]

Once it's built once, even a clean/build with netbeans works.

The problem is very likely how netbeans is executing the ld generation then. There was a valid bug in ldgen.py but only if it encountered a file that did not have the type in it that was expected. It was a very specific pattern and it is entirely possible that netbeans is using an older copy of the files that did not have the fix included.