On 2026-11-03 06:02, Marcus Hähnel wrote:
So you did `make oldconfig` and / or a global make from the root directory? See also the other mail. Just doing `make S=pkg/foo/bar` will not build dependencies. `make pkg/foo/bar` will and should trigger a build of the libgcc_s.
Starting with a new build directory, I configured the target and then ran the following: make -j O=mybuild This caused the problem with libgcc_s. Doing a make on a specific package but without setting S is also quite helpful, which I didn't realise, but this generated the same error. Doing "make oldconfig" didn't seem to make much of a difference.
To check if the rules have been regenerated correctly by `make oldconfig` have a look into .Package.deps in the build dir. All programs build shared, and all libraries that also have a shared variant (.so) should depend on `stdlibs-sh` which depends on `libgcc_s`. I checked on my build tree and this is the case for me.
This may be the problem. If I add stdlibs-sh to the Control file, the problem appears to be resolved. [...]
This looks correct. Please check .Package.deps.
.Package.deps was helpful, making me think that I might need to depend on libdl, but your suggestion seems to be more appropriate. As for the matter of reporting errors, perhaps a sensible approach might involve each package writing its build outcome (or a build failure) to a centrally located directory. Then, either make or the developer themself could at least inspect these outcomes by perusing that directory. Thanks for the help! Paul