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 18:04:13 +0200 [thread overview]
Message-ID: <87k7ud9fgi.fsf@fadata.bg> (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>
>>>>> "Adrian" == Adrian Bunk <bunk@fs.tum.de> writes:
Adrian> If your compiler is configured as a cross-compiler everything should work
Adrian> as expected. If you are trying to compile a Linux kernel with a gcc that
Adrian> is configured to build binaries for NetBSD this sounds evil.
Could you elaborate why ? I think people do it all the time, compiling
linux (which is not a _linux_ binary, but a i386, alpha, etc. binary)
with a compiler configured to compile linux binaries.
>> >> __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 ?
Adrian> I don't know (I never tried to compile a *BSD kernel).
Adrian> But if yes please consider what the following parts of your patch change:
Adrian> -#ifndef __linux__
Adrian> +#ifndef __KERNEL__
I have. Have you ?
Regards,
-velco
next prev parent reply other threads:[~2002-01-20 16:04 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 [this message]
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=87k7ud9fgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.