Thu, Nov 12, 2015 at 09:29:37PM +0100, Eric Le Bihan wrote: > Comments welcomed!
depends on BR2_TOOLCHAIN_USES_GLIBC || BR2_TOOLCHAIN_USES_MUSL looks really strange, uClibc is typically the least problematic libc. I can definitely build it with a uclibc toolchain, all it needs is -lrt in skalibs configure when testing for posix_spawn* and later whenever -lskalibs is used. It does not work though. What I have so far is this: execve("/usr/sbin/s6-echo", ["s6-echo", "--", "Starting system."], ...) execve("s6-echo", ["s6-echo", "--", "Starting system."], ...) execve("s6-echo", ["s6-echo", "--", "Starting system."], ...) execve("s6-echo", ["s6-echo", "--", "Starting system."], ...) execve("s6-echo", ["s6-echo", "--", "Starting system."], ...) ... and it keeps repeating that execve in an infinite loop. That's execline running /sbin/init. The first if and the first occurence of a { } block in that script. Strange, but I did not look further into this yet. > buildroot-s6 is a sandbox to play with the s6 stack and see how it could be > integrated into the official Buildroot. It is still a work-in-progress. The worst part will be dealing with per-package service files. I did try doing similar thing. Ended up with all my stuff in BR2_EXTERNAL, this way it's much easier to keep Buildroot proper up to date.