From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Issue preparing a buildroot
Date: Tue, 12 Dec 2006 17:05:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20061212T180342-945@post.gmane.org> (raw)
In-Reply-To: 1165937001.6628.13.camel@petitemort.i.digital-scurf.org
Daniel Silverstone <dsilvers@...> writes:
> Well, except for the fact that the kernel team explicitly state that
> linux/limits.h belongs to *LINUX* not to userland
>
> D.
>
I /did/ mean the kernel limits.h, not the standard C lib one.
Mike
prev parent reply other threads:[~2006-12-12 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 10:33 [Buildroot] Issue preparing a buildroot Daniel Silverstone
2006-12-12 15:09 ` MikeW
2006-12-12 15:23 ` Daniel Silverstone
2006-12-12 17:05 ` MikeW [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20061212T180342-945@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox