From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andries.Brouwer@cwi.nl
Cc: Dominik.Strasser@t-online.de, hch@infradead.org,
jgarzik@pobox.com, linux-kernel@vger.kernel.org,
torvalds@osdl.org
Subject: Re: headers
Date: Mon, 18 Aug 2003 14:57:09 -0700 [thread overview]
Message-ID: <20030818145709.0b5e162a.rddunlap@osdl.org> (raw)
In-Reply-To: <UTC200308181907.h7IJ7im12407.aeb@smtp.cwi.nl>
On Mon, 18 Aug 2003 21:07:44 +0200 (MEST) Andries.Brouwer@cwi.nl wrote:
| From garzik@gtf.org Mon Aug 18 20:14:47 2003
|
| I support include/abi, or some other directory that segregates
| user<->kernel shared headers away from kernel-private headers.
|
| I don't see how that would be auto-generated, though. Only created
| through lots of hard work :)
|
| Yes, unfortunately. I started doing some of this a few times,
| but it is an order of magnitude more work than one thinks at first.
I expected that.
| Already the number of include files is very large.
| And the fact that it is not just include/abi but involves the architecture
| doesn't make life simpler.
|
| No doubt we must first discuss a little bit, but not too much,
| the desired directory structure and naming.
| Then we must do 5% of the work, and come back to these issues.
|
| In case people actually want to do this, I can coordinate.
|
| In case people want to try just one file, do signal.h.
Hm, interesting.
Since there are 20+ <arch>/signal.h files and they don't always agree
on signal bit numbers e.g., do we have 20+ abi/arch/signal.h files?
Or 1 abi/signal.h file with many #ifdefs? ugh.
The ABI is still per-arch, right? Not _one ABI_ for any/all arches.
Or maybe I'm all wet.
--
~Randy
"Everything is relative."
next prev parent reply other threads:[~2003-08-18 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:07 headers Andries.Brouwer
2003-08-18 21:57 ` Randy.Dunlap [this message]
2003-08-18 22:04 ` headers Jeff Garzik
2003-08-18 22:17 ` headers Andries Brouwer
2003-08-19 1:45 ` headers H. Peter Anvin
2003-08-19 12:55 ` headers Rob Landley
2003-08-19 15:45 ` headers Randy.Dunlap
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=20030818145709.0b5e162a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=Dominik.Strasser@t-online.de \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).