Hi, Vincent Legoll <vincent.leg...@gmail.com> writes:
>>> We usually don’t use the “gcc” package directly in Guix. Instead we use >>> “gcc-toolchain”, which also comes with a wrapper around the linker that >>> ensures that binaries are linked with libraries in the store, ensuring >>> that things generally just work™. >>> >>> I think more work would be needed to ensure that packages can actually >>> successfully be linked with musl, but I’m not at all familiar with this. >>> I had mixed success with a GCC ARM cross-compiler toolchain linking with >>> newlib, so I know that it’s not exactly obvious how to do this right, >>> but I find it hard to understand this. >>> >>> Have you tried building something that links with the libc provided by >>> this musl package instead of the GNU libc? I’m not opposed to adding >>> the package, but I’d like it to be usable. > > I'm not sure... > > I built musl, made the sinit package use the musl-wrapper as CC, > and it worked (it builds => it works) but couldn't test that sinit as > replacement for pid 1... I was wondering what happened to musl? Are there any problems left, anything the people you have been working with can help you to solve? I had the impression it was almost ready. > -- > Vincent Legoll
