From: "David S. Miller" <davem@redhat.com>
To: thomas@horsten.com
Cc: hch@infradead.org, voidcartman@yahoo.com,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial)
Date: Tue, 06 May 2003 22:53:42 -0700 (PDT) [thread overview]
Message-ID: <20030506.225342.68058619.davem@redhat.com> (raw)
In-Reply-To: <200305070759.49121.thomas@horsten.com>
From: Thomas Horsten <thomas@horsten.com>
Date: Wed, 7 May 2003 07:59:49 +0100
On Wednesday 07 May 2003 7:45 am, Christoph Hellwig wrote:
> That's highly broken because his libc was compiled against 2.2 headers.
> You must never use different headers in /usr/include/Pasm,linux}
> then those your libc was compiled against.
I don't see why moving up should be wrong -
The headers used for 2.2.x era libc cannot cope with or conflit with
many of the constructs used by current kernel headers.
Chritoph's points are very real.
next prev parent reply other threads:[~2003-05-07 6:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 9:16 [PATCH] 2.4.21-rc1: byteorder.h breaks with __STRICT_ANSI__ defined (trivial) Thomas Horsten
2003-05-06 9:19 ` David S. Miller
2003-05-06 9:38 ` Christoph Hellwig
2003-05-06 9:47 ` Thomas Horsten
2003-05-06 9:49 ` Christoph Hellwig
2003-05-06 10:03 ` David S. Miller
2003-05-06 14:10 ` Thomas Horsten
2003-05-06 13:06 ` David S. Miller
2003-05-06 15:40 ` Thomas Horsten
2003-05-07 5:50 ` ismail (cartman) donmez
2003-05-07 6:44 ` Thomas Horsten
2003-05-07 6:45 ` Christoph Hellwig
2003-05-07 5:44 ` David S. Miller
2003-05-07 6:55 ` Christoph Hellwig
2003-05-07 6:59 ` Thomas Horsten
2003-05-07 5:53 ` David S. Miller [this message]
2003-05-06 21:19 ` David Woodhouse
2003-05-07 3:06 ` David S. Miller
2003-05-07 5:26 ` Christoph Hellwig
2003-05-07 5:07 ` David S. Miller
2003-05-07 6:20 ` Christoph Hellwig
2003-05-07 5:19 ` David S. Miller
2003-05-07 6:28 ` Christoph Hellwig
2003-05-07 5:27 ` David S. Miller
2003-05-07 6:41 ` Christoph Hellwig
2003-05-07 5:42 ` David S. Miller
[not found] <20030506110259.A29633@infradead.org>
2003-05-06 10:24 ` Thomas Horsten
2003-11-06 17:36 Martin Schlemmer
2003-11-06 17:37 ` David S. Miller
2003-11-06 18:32 ` Martin Schlemmer
2003-11-06 18:42 ` Martin Schlemmer
2003-11-06 19:37 ` David S. Miller
2003-11-06 20:09 ` Martin Schlemmer
2003-11-06 20:05 ` David S. Miller
2003-11-06 20:29 ` Martin Schlemmer
2003-11-06 20:27 ` David S. Miller
2003-11-06 21:18 ` Martin Schlemmer
2003-11-06 21:18 ` David S. Miller
2003-11-06 21:59 ` Martin Schlemmer
2003-11-06 21:24 ` Daniel Jacobowitz
2003-11-06 20:40 ` H. Peter Anvin
2003-11-06 22:31 ` David S. Miller
2003-11-06 23:40 ` H. Peter Anvin
2003-11-06 21:21 ` Daniel Jacobowitz
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=20030506.225342.68058619.davem@redhat.com \
--to=davem@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=thomas@horsten.com \
--cc=voidcartman@yahoo.com \
/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).