From: Momchil Velikov <velco@fadata.bg>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] __linux__ and cross-compile
Date: 20 Jan 2002 17:08:38 +0200 [thread overview]
Message-ID: <87sn919i15.fsf@fadata.bg> (raw)
In-Reply-To: <Pine.NEB.4.44.0201201519460.20948-100000@mimas.fachschaften.tu-muenchen.de>
In-Reply-To: <Pine.NEB.4.44.0201201519460.20948-100000@mimas.fachschaften.tu-muenchen.de>
>>>>> "Adrian" == Adrian Bunk <bunk@fs.tum.de> writes:
Adrian> On 20 Jan 2002, Momchil Velikov wrote:
>> Hi there,
>>
>> The following patch fixes compilation/miscompilation problems, which
>> may happend iwtg variuos cross compile configuration, wherte the
>> compiler used to compile the kernel does not necessarily define
>> __linux__. The patch replaces __linux__ with __KERNEL__, using
Adrian> Isn't this a compiler bug?
Why would it be ? I may want to cross-compile from, e.g., NetBSD with
the host compiler, or I may want compile from GNU/Linux, but with a
compiler like arm-elf-gcc, that is, generic arm cross compiler, used
for other kernels too.
>> __KERNEL_ as an indication that the source is compiled as a part of
>> ...
Adrian> This is definitely wrong in files that are not Linux-specific and that are
Adrian> used on FreeBSD (and BSDI) as well (you would know that if you'd looked at
Adrian> the files your patch changes)...
*BSD define _KERNEL, don't they ?
Regards,
-velco
next prev parent reply other threads:[~2002-01-20 15:09 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 [this message]
2002-01-20 15:17 ` Adrian Bunk
2002-01-20 16:04 ` Momchil Velikov
2002-01-20 16:15 ` David Woodhouse
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=87sn919i15.fsf@fadata.bg \
--to=velco@fadata.bg \
--cc=bunk@fs.tum.de \
--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