Hi Paul, On 2026-11-02 19:06, Paul Boddie wrote:
On 2026-11-02 11:12, Paul Boddie wrote:
I've been trying to update my code to work with the latest L4Re sources, along with some older L4Re code that still resides in Subversion, but I seem to be encountering this error:
mipsel-linux-gnu-ld: cannot find -lgcc_s: No such file or directory
Just following up on this, if I explicitly build libgcc_s...
make O=mybuild V=1 S=pkg/l4re-core/libgcc_s
...and then build the specific package that is failing, then it does get built. So, I am suspecting that the "requires" specification in my Control file is not causing the build order to be properly established. As a low-level library, it only depends on the following packages:
l4re_c l4sys
Is this no longer sufficient?
Interesting, that should still be enough. Just to be sure, you did a `make oldconfig` after the update in the root directory and did either a global make or did build the failing package with dependency resolution (so `make pkg/path/to/package` instead of `make S=pkg/path/to/pkg`)? 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. If oldconfig / dedicated make did not help, can your show me what the output value of the `CONFIG_COMPILER_RT_*` options are (see .config in the build dir). And check the dependency file in the build tree (.Package.deps). compiler-rt-shared should pull libgcc_s in, and your program that fails to link, likely links in shared mode (program with MODE=shared, or shared lib).
Another thing, since I'm here: is it possible to make the build exit in a clean way and indicate the packages that caused errors, as opposed to having to peruse hundreds or even thousands of lines of output? This has constantly been a problem when developing for L4Re.
Yes, I had some thoughts on that in the past. It is not straight forward, because the builds happen in parallel and there are multiple possible entry points to such parallel builds, but I might revisit that in the future. This would be helpful (and maybe even having a per pkg build log available for the failed packages). But I cannot make any promises on a timeline :)
Thanks for any help that might be offered,
I hope the ideas above already help. Please let me know more details if it doesn't. Best, - Marcus
Paul _______________________________________________ l4-hackers mailing list -- l4-hackers@os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave@os.inf.tu-dresden.de