From: Dick <dm@chello.nl>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] broken kernel headers
Date: Tue, 2 May 2006 19:25:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20060502T210232-275@post.gmane.org> (raw)
Hi all,
I'm compiling some software created for Fedora/Red Hat and discovered some of
the gentoo kernel-headers are broken.
For example ethtool.h, which uses the u32 typedef defined in asm/types.h. This
typedef has been disabled outside the kernel "to avoid name space clashes" which
I think is a Good Thing.
Inspired by this header I dug into sys-apps/ethtool and found this package used
a copy of an old ethtool.h and a ethtool_util.h which typedef'ed the missing
types.
I don't think this is a bad choice but it makes ethtool.h obsolete and still
broken.
I thought it might be better to remove the broken headers completely or fix them
up and/ or patch ebuild's like ethtool to use the real kernel-headers.
Red Hat / Fedora provide heavily modified kernel headers (glibc-kernheaders)
maybe we can borrow some patches from them...
What would be the best way to deal with these broken kernel headers? (plasmaroo?)
Greetings,
Dick
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-05-02 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:25 Dick [this message]
2006-05-03 0:26 ` [gentoo-dev] broken kernel headers Mike Frysinger
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.20060502T210232-275@post.gmane.org \
--to=dm@chello.nl \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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