On 2026-11-02 18:31, Marcus Haehnel wrote:
I wonder a bit why your l4re-core/libgcc_s directory comes from, which you build with the make command you cite above. There is no such directory and never has been. Is this maybe something you have locally? Or did you mean S=pkg/l4re-core/libgcc?
No, this is a real directory! It was installed by ham when I ran these commands: ham init -u https://github.com/kernkonzept/manifest.git ham sync
Usually things like libgcc come in through the compiler-rt .pc file (see pc directory in the build dir) and depend on your config (i.e. if you use the toolchain libgcc or the ones from l4re-core). The compiler-rt should be pulled in by other packages, usually there is no need to directly depend on it.
Did you make an `make oldconfig` after the update, to make sure the configuration is up to date? Usually we default to using our supplied libgcc nowadays but the build must be correctly configured for this to work.
I probably should have noted this, but I was populating the build tree from scratch, also copying my own packages into the pkg directory. I don't really know how to use ham beyond setting up the packages in the manifest, so I couldn't say where I might have gone wrong. [Errors]
Sadly this is not easy due to the parallel building inside the packages. But I have thought about this before and might put it higher on my agenda that your main make that triggered the build reads a result file for failed packages. But it is not straight forward to do this.
I appreciate that it is difficult, certainly. Make isn't the easiest tool to work with.
Please let me know if anything of the above (i.e. the `oldconfig`) helped, and if not please let me know how your L4Re is configured, in particular what the settings of the `CONFIG_COMPILER_RT_*` options are.
From mybuild/.config: CONFIG_COMPILER_RT_CHOICE_AUTO=y CONFIG_COMPILER_RT_USE_LIBGCC=y Thanks for the response! Paul