Volodymyr Shymanskyy

It turns out, that some `.a` and `.so` files are actually LD scripts... Here's how my `/usr/lib/x86_64-linux-gnu/libm.a` looks like: ```c /* GNU ld script */ OUTPUT_FORMAT(elf64-x86-64) GROUP ( /usr/lib/x86_64-linux-gnu/libm-2.38.a /usr/lib/x86_64-linux-gnu/libmvec.a...

Thanks for comments, I think these are all very relevant. Regarding size increase, it wont happen automatically, the developer will have to explicitly use this feature. But the docs need...

I don't think `ar` depends on `Python 3.11`, as it's [verified for versions back to 3.7](https://github.com/vidstige/ar/actions/runs/10828329931). However, I didn't test the code of my PR for such compatibility. I'll start...

@jonnor yes, that was used in my code. But it's already fixed in the latest version of this PR. I'm now fixing other CI tests.

@jonnor please try the latest version. These symbols are weak and `mpy_ld` never really handled them. I added some basic support for weak symbols, but it should be addressed via...

The documentation and CI tests are added. One test fails: `esp32 port / build_idf (esp32_build_cmod_spiram_s2)` This is due to `Cached ESP-IDF install`. Once cache is dropped, all should work as...

@jonnor as I mentioned, mpy_ld never actually handled weak symbols so this is expected. Most probably, your other modules have these symbols defined explicitly. Could you check if that's the...

I have temporarily removed the IDF installation cache, to verify the PR. **All checks have passed**

This happens because the `lib_a-s_lib_ver.o` has a non-empty data section, and currently `mpy_ld` doesn't support this (as stated in the documentation). These limitations still apply to static libraries. This not...

@agatti I'm pretty sure that `-specs` DOES have impact on `--print-file-name`.