mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bodnar42@bodnar42.dhs.org (Ryan Cumming)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	jaharkes@cs.cmu.edu (Jan Harkes),
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/linux/coda.h
Date: Tue, 22 May 2001 19:06:42 +0100 (BST)	[thread overview]
Message-ID: <E152GYM-0002GF-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0105220924560.32368-100000@bodnar42.dhs.org> from "Ryan Cumming" at May 22, 2001 09:40:19 AM

> When compiling the kernel under FreeBSD, __KERNEL__ is defined, but
> __linux__ is not. I think this is an error on the part of the header file,
> because on non-Linux build environments, which would otherwise compile the
> Linux kernel correctly, do not have __linux__ defined.

Thats a problem with your compiler setup.

> However, not many people will probably find much use in compiling the
> kernel on other platforms, so if you think this isn't worth inclusion, I
> totally understand. I'm in the process of porting UML to FreeBSD, and
> having this patch in the tree would make my job slightly easier.

Teaching your gcc to do -D__linux__ would be cleaner and also catch the
zillion other cases that simply came out wrong instead of erroring

One shell script for your CC and off you go



  parent reply	other threads:[~2001-05-22 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22  4:24 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
2001-05-22 18:06         ` Alan Cox [this message]
2001-05-24 17:33         ` [PATCH] include/linux/coda.h 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=E152GYM-0002GF-00@the-village.bc.nu \
    --to=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

all inboxes | Powered by JetHome®