From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Ryan Cumming <bodnar42@bodnar42.dhs.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, Jeff Dike <jdike@karaya.com>
Subject: UML cross-platform build problems (was Re: [PATCH] include/linux/coda.h)
Date: Tue, 22 May 2001 12:56:26 -0400 [thread overview]
Message-ID: <20010522125625.A3985@cs.cmu.edu> (raw)
In-Reply-To: <E152DEZ-0001y7-00@the-village.bc.nu> <Pine.LNX.4.33L2.0105220924560.32368-100000@bodnar42.dhs.org>
In-Reply-To: <Pine.LNX.4.33L2.0105220924560.32368-100000@bodnar42.dhs.org>; from bodnar42@bodnar42.dhs.org on Tue, May 22, 2001 at 09:40:19AM -0700
On Tue, May 22, 2001 at 09:40:19AM -0700, Ryan Cumming wrote:
> On Tue, 22 May 2001, Alan Cox wrote:
>
> > 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 ?
>
> It is not a cross compiler, it is the FreeBSD native gcc. As I understood
> it, Linux is a self contained project and should be targetting the
> native platform, not Linux on that platform. A cross compiler should
> not be needed unless one is building for another CPU.
The problem is that the same coda.h header is also used as part of the
FreeBSD kernel to build a Coda kernel module. Both Linux and FreeBSD
have different include and typedef requirements for their kernel code.
There is no way for an identical coda.h header to recognize whether it
is built as part of the FreeBSD kernel or as part of a (UML) Linux
kernel, except if the parts that are OS dependent are not part of the
same header.
I agree that a UML kernel on FreeBSD should be a native binary and not
cross-compiled. However, this could be an UML specific problem and
-D__linux__ should be added to CFLAGS in arch/uml/Makefile as all
drivers and filesystems that are developed for different platforms and
share parts of their code are possibly affected.
Jan
next prev parent reply other threads:[~2001-05-22 16:57 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
2001-05-22 16:40 ` Ryan Cumming
2001-05-22 16:56 ` Jan Harkes [this message]
2001-05-22 20:13 ` UML cross-platform build problems (was Re: [PATCH] include/linux/coda.h) 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=20010522125625.A3985@cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bodnar42@bodnar42.dhs.org \
--cc=jdike@karaya.com \
--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