From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: bodnar42@bodnar42.dhs.org (Me), jaharkes@cs.cmu.edu (Jan Harkes),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/linux/coda.h
Date: Tue, 22 May 2001 16:57:24 +0100 [thread overview]
Message-ID: <26524.990547044@redhat.com> (raw)
In-Reply-To: <E152DEZ-0001y7-00@the-village.bc.nu>
In-Reply-To: <E152DEZ-0001y7-00@the-village.bc.nu>
alan@lxorguk.ukuu.org.uk said:
> Why is your cross compiler outputting different symbols to a linux
> native compiler ?
> If __linux__ is not defined by the cross compiler, then the cross
> compiler is broken. A cross compiler has the same environment as the
> native compiler for the target. The only stuff that should break (well
> should as in might) is tools native built
> Or am I misunderstanding the report ?
Why use a cross compiler? With the obvious exception of UML, the Linux
kernel is not a Linux executable, so why should it need to be compiled with
a compiler which targets such?
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.
--
dwmw2
next prev parent reply other threads:[~2001-05-22 15:58 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 [this message]
2001-05-22 16:22 ` Jan Harkes
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=26524.990547044@redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bodnar42@bodnar42.dhs.org \
--cc=jaharkes@cs.cmu.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.