From: David Woodhouse <dwmw2@infradead.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Momchil Velikov <velco@fadata.bg>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __linux__ and cross-compile
Date: Sun, 20 Jan 2002 16:15:02 +0000 [thread overview]
Message-ID: <2385.1011543302@redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0201201611030.20948-100000@mimas.fachschaften.tu-muenchen.de>
In-Reply-To: <Pine.NEB.4.44.0201201611030.20948-100000@mimas.fachschaften.tu-muenchen.de>
bunk@fs.tum.de said:
> If your compiler is configured as a cross-compiler everything should
> work as expected. If you are trying to compile a Linux kernel with a
> gcc that is configured to build binaries for NetBSD this sounds evil.
What if he's trying to build UML to run on NetBSD? What if the best QA'd
cross-gcc he has available is a generic arm-elf-gcc and he doesn't want to
rebuild and do a full test and release cycle on it just because a handful
of the kernel header files assume __linux__ will be defined?
> I don't know (I never tried to compile a *BSD kernel).
If you don't know, who was it that typed 'This is definitely wrong' in your
first mail? Your cat?
> But if yes please consider what the following parts of your patch change:
> -#ifndef __linux__
> +#ifndef __KERNEL__
Well, if he hadn't explicitly mentioned that he made header files which
could be included by userspace use defined(__KERNEL__)||defined(__linux__)
then I'd understand what you meant. As it is, I don't. Please explain.
--
dwmw2
next prev parent reply other threads:[~2002-01-20 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 13:59 [PATCH] __linux__ and cross-compile Momchil Velikov
2002-01-20 14:23 ` Adrian Bunk
2002-01-20 15:08 ` Momchil Velikov
2002-01-20 15:17 ` Adrian Bunk
2002-01-20 16:04 ` Momchil Velikov
2002-01-20 16:15 ` David Woodhouse [this message]
2002-01-20 16:29 ` Adrian Bunk
2002-01-20 16:37 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 7:43 Zwane Mwaikambo
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=2385.1011543302@redhat.com \
--to=dwmw2@infradead.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=velco@fadata.bg \
/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