From: Andrew Walrond <andrew@walrond.org>
To: David Miller <davem@davemloft.net>
Cc: jengelh@medozas.de, sam@ravnborg.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.28 headers break kbd and net-tools userspace builds
Date: Mon, 02 Feb 2009 21:13:11 +0000 [thread overview]
Message-ID: <498761E7.3080006@walrond.org> (raw)
In-Reply-To: <20090202.120507.152093960.davem@davemloft.net>
David Miller wrote:
>
> There isn't anything we can really do about these cases.
>
> No matter what we do, we break the userland build in one way or
> another.
>
What exactly is the purpose of the kernel headers? Are there some
definitions in the kernel headers that will never be available from
glibc? Is it perhaps possible to work towards exporting kernel headers
for the sole purpose of building glibc, and all other packages should be
able to build against glibc's headers?
Andrew Walrond
next prev parent reply other threads:[~2009-02-02 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49786A59.6040706@walrond.org>
[not found] ` <20090122175645.GA14178@uranus.ravnborg.org>
[not found] ` <4978C301.1040705@walrond.org>
2009-01-22 19:12 ` 2.6.28 headers break kbd and net-tools userspace builds Sam Ravnborg
2009-01-27 5:08 ` David Miller
2009-01-27 10:44 ` Jan Engelhardt
2009-01-28 20:29 ` David Miller
2009-01-30 4:12 ` Jan Engelhardt
2009-02-02 10:35 ` Andrew Walrond
2009-02-02 20:05 ` David Miller
2009-02-02 21:13 ` Andrew Walrond [this message]
2009-02-02 21:24 ` David Miller
2009-02-02 21:27 ` David Miller
2009-02-03 4:58 ` Sam Ravnborg
2009-02-03 5:26 ` David Miller
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=498761E7.3080006@walrond.org \
--to=andrew@walrond.org \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.org \
/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;
as well as URLs for NNTP newsgroup(s).