[klibc] sample sleep command killed
kunnskaperen at gmail.com
Fri Jul 16 04:23:07 PDT 2010
On Fri, Jul 16, 2010 at 6:19 AM, maximilian attems <max at stro.at> wrote:
> I think your question is more anchored in the old tradition of
> bigger unixes with several users sharing /usr/src/
> these days a ~/src/ with your own compiled stuff eases dev.
My script configures a kernel source tree and installs the headers
into an adjacent working directory. /usr/src is entirely ignored as
long as the Klibc build system will ignore it when directed to the
temporary install of headers.
And my builds happen on machines with no net access. Live git pulls
won't be an option. That, and I'd never do automated builds that way
unless I was targeting a specific revision. What I might do is git
pulls and make a tarball identified by the revision (a faux release
version) just for my own processes.
My concern with this mailing list is the underlying build of Klibc,
and how to use Klibc. My own build infrastructure isn't an issue
here. It's my responsibility to find out how to make Klibc build
right, and be sure my scripts do it. If I run into any bugs and
figure out a fix, I'll also contrib them back and they can be
evaluated and maybe used. I'm not intending specifically to do any
development of Klibc itself, unless I need to use an architecture it
does not yet support. My use for Klibc is to support my own early
user space code development so I don't have to deal with generating
raw syscalls and such.
More information about the klibc