From: Jan Harkes <jaharkes@cs.cmu.edu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Me <bodnar42@bodnar42.dhs.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/linux/coda.h
Date: Tue, 22 May 2001 12:22:39 -0400 [thread overview]
Message-ID: <20010522122239.A32535@cs.cmu.edu> (raw)
In-Reply-To: <E152DEZ-0001y7-00@the-village.bc.nu> <26524.990547044@redhat.com>
In-Reply-To: <26524.990547044@redhat.com>; from dwmw2@infradead.org on Tue, May 22, 2001 at 04:57:24PM +0100
On Tue, May 22, 2001 at 04:57:24PM +0100, David Woodhouse wrote:
> The kernel compiles quite happily with compilers which aren't targetted
> specifically at Linux -- the CODA compatibility cruft being the one
> exception. I often just comment out the CODA includes from <linux/fs.h> to
> get round the same problem.
Well, the original idea for having all that compatibility cruft in
coda.h was that the identical header could be used both by userspace,
and as part of the kernel code of all Coda ports.
But with problems like these popping up and the silly thing is just
turning into an unmaintainable mess of #ifdef bloat.
#include <linux/coda.h> can be taken out of linux/fs.h when I change a
few lines of code. In fact with those changes all Coda related headers
can be moved from include/linux/ to fs/coda/, although coda.h contains
the 'exported interface' and should probably remain in include/linux.
At least this will solve your problem as long as Coda isn't compiled
into the kernel, but not the reported problem of compiling a Linux
kernel on a different (Coda supported) OS without using a properly
configured cross-compiler.
I will try cleaning things up by having a common 'coda.h' for all
platforms (and userspace) and platform specific 'coda_types.h' files
which define missing types and such. It would definitely get rid of a
lot of the bloat, and probably make things somewhat easier to maintain.
Jan
btw. Coda is not an acronym, no need to capitalize it.
next prev parent reply other threads:[~2001-05-22 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 4:24 [PATCH] include/linux/coda.h Me
2001-05-22 13:18 ` Jan Harkes
2001-05-22 14:21 ` Me
2001-05-22 14:34 ` Alan Cox
2001-05-22 15:57 ` David Woodhouse
2001-05-22 16:22 ` Jan Harkes [this message]
2001-05-22 16:40 ` Ryan Cumming
2001-05-22 16:56 ` UML cross-platform build problems (was Re: [PATCH] include/linux/coda.h) Jan Harkes
2001-05-22 20:13 ` Jeff Dike
2001-05-22 18:06 ` [PATCH] include/linux/coda.h Alan Cox
2001-05-24 17:33 ` Thomas Dodd
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=20010522122239.A32535@cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bodnar42@bodnar42.dhs.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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