public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Ryan Cumming <bodnar42@bodnar42.dhs.org>
Cc: Jan Harkes <jaharkes@cs.cmu.edu>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: UML cross-platform build problems (was Re: [PATCH]  include/linux/coda.h)
Date: Tue, 22 May 2001 15:13:52 -0500	[thread overview]
Message-ID: <200105222013.PAA03768@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 22 May 2001 12:56:26 -0400." <20010522125625.A3985@cs.cmu.edu>

jaharkes@cs.cmu.edu said:
> 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

Exactly.  Don't be shy about fiddling CFLAGS in UML-specific Makefiles.  This 
is already done quite a bit (-D__i386__ and the construction of userspace 
CFLAGS are examples).

This is very UML-specific, so there's no reason to bother the rest of the 
kernel (unless, of course, you find a bug that could affect other ports).

				Jeff



  reply	other threads:[~2001-05-22 20:29 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         ` UML cross-platform build problems (was Re: [PATCH] include/linux/coda.h) Jan Harkes
2001-05-22 20:13           ` Jeff Dike [this message]
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=200105222013.PAA03768@ccure.karaya.com \
    --to=jdike@karaya.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox