From: Stefan Rompf <stefan@loplof.de>
To: Thomas Graf <tgraf@suug.ch>
Cc: David Woodhouse <dwmw2@infradead.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
netdev@vger.kernel.org, libc-alpha@sourceware.org, akpm@osdl.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Kernel header changes break glibc build
Date: Wed, 6 Dec 2006 20:32:40 +0100 (MET) [thread overview]
Message-ID: <200612062033.34754.stefan@loplof.de> (raw)
In-Reply-To: <20061204091341.GM8693@postel.suug.ch>
Am Montag, 4. Dezember 2006 10:13 schrieb Thomas Graf:
> I do not agree with the change to include if_addr.h in rtnetlink.h.
> The point is to move bits apart and have multiple small pieces
> of header files defining a specific rtnetlink family which are a
> lot easier to maintain for both kernel and userspace than one giant
> rtnetlink.h for everything.
According to a user's report, your change also broke compilation of my
dhcpclient because it neeeds if_addr.h since 2.6.19. Any suggestion how to
make one source code build on 2.6.19 and older headers? I hope you don't want
me to check on UTS_RELEASE in a userspace program?
Stefan
next prev parent reply other threads:[~2006-12-06 19:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 17:20 Kernel header changes break glibc build Joseph S. Myers
2006-12-03 12:25 ` David Woodhouse
2006-12-04 9:13 ` Thomas Graf
2006-12-06 13:01 ` David Woodhouse
2006-12-06 13:43 ` Jakub Jelinek
2006-12-06 13:51 ` David Woodhouse
2006-12-06 13:57 ` Jakub Jelinek
2006-12-06 14:01 ` David Woodhouse
2006-12-06 13:59 ` Thomas Graf
2006-12-06 14:07 ` David Woodhouse
2006-12-06 14:18 ` Jakub Jelinek
2006-12-06 14:31 ` Thomas Graf
2006-12-06 17:13 ` Al Viro
2006-12-06 20:26 ` Thomas Graf
2006-12-06 20:34 ` Al Viro
2006-12-06 21:35 ` Thomas Graf
2006-12-06 14:23 ` Thomas Graf
2006-12-07 11:29 ` David Woodhouse
2006-12-06 19:32 ` Stefan Rompf [this message]
2006-12-06 20:22 ` Thomas Graf
2006-12-07 0:56 ` David Miller
2006-12-07 10:47 ` Thomas Graf
2006-12-07 10:51 ` David Miller
2006-12-07 10:55 ` [NETLINK]: Restore API compatibility of address and neighbour bits Thomas Graf
2006-12-07 11:28 ` David Woodhouse
2006-12-08 7:52 ` David Miller
2006-12-08 7:50 ` David Miller
2006-12-08 14:25 ` Stefan Rompf
2006-12-08 17:33 ` Jim Gifford
2006-12-08 17:54 ` Mike Frysinger
2006-12-08 21:33 ` David Miller
2006-12-08 21:36 ` Daniel Jacobowitz
2006-12-08 21:47 ` David Miller
2006-12-08 21:52 ` Daniel Jacobowitz
2006-12-09 0:43 ` David Miller
2006-12-09 1:14 ` David Miller
2006-12-09 10:39 ` [NETLINK]: Schedule removal of old macros exported to userspace Thomas Graf
2006-12-09 11:49 ` Stefan Rompf
2006-12-09 12:55 ` Thomas Graf
2006-12-09 14:58 ` Stefan Rompf
2006-12-09 21:50 ` David Miller
2006-12-09 22:02 ` David Woodhouse
2006-12-12 11:23 ` David Woodhouse
2006-12-09 21:49 ` David Miller
2006-12-09 21:45 ` David Miller
2006-12-09 23:28 ` Thomas Graf
2006-12-10 10:11 ` Stefan Rompf
2006-12-10 12:15 ` Thomas Graf
2006-12-12 6:56 ` dhcpclient netlink bugs (was Re: [NETLINK]: Schedule removal of old macros exported to userspace) Stefan Rompf
2006-12-15 0:46 ` Herbert Xu
2006-12-10 1:42 ` [NETLINK]: Schedule removal of old macros exported to userspace Jeff Bailey
2006-12-10 1:52 ` Al Viro
2006-12-09 9:56 ` [NETLINK]: Restore API compatibility of address and neighbour bits Stefan Rompf
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=200612062033.34754.stefan@loplof.de \
--to=stefan@loplof.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).