tmedicci commented on PR #2026: URL: https://github.com/apache/nuttx-apps/pull/2026#issuecomment-2140491451
@acassis , this issue is not related directly to ESP32-S2 or ESP32-S3, neither with xtensa-only devices. Please check [this comment](https://github.com/apache/nuttx-apps/pull/2026#issuecomment-1880299715): there is still pending work. While this is incomplete, `sotest` will fail to be built and work as expected. The error message is (for RISC-V, for instance): ``` riscv-none-elf-ld: /nuttx/nuttxspace/nuttx/staging/libapps.a(sot_symtab.c.nuttx.nuttxspace.apps.examples.sotest_1.o):(.rodata.g_sot_exports+0x4): undefined reference to `_start' ``` `_start` refers to an undefined symbol in `apps/examples/sotest/lib/fsroot/dynload`. `mksymtab` generates the following content to the `apps/examples/sotest/lib/sot_symtab.c`: ``` #include <nuttx/compiler.h> #include <nuttx/symtab.h> extern void *_start; extern void *syslog; extern void *vsyslog; const struct symtab_s g_sot_exports[] = { {"_start", &_start}, {"syslog", &syslog}, {"vsyslog", &vsyslog}, }; const int g_sot_nexports = sizeof(g_sot_exports) / sizeof(struct symtab_s); ``` There is no relation to `__esp32s3_start` or `__start` as @almir-okato said. I am submitting a PR to revert this until we have it properly fixed. In this case, CI was able to capture the errors (I could not check because the artifacts are gone, but it is a build issue) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
