mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kenn Humborg" <kenn@bluetree.ie>
To: "Petr Baudis" <pasky@ucw.cz>, "Peter Samuelson" <peter@cadcamlab.org>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
	"kbuild-devel" <kbuild-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [kbuild-devel] Re: [PATCH] [kbuild] Possibility to sanely link against off-directory .so
Date: Thu, 7 Nov 2002 16:20:34 -0000	[thread overview]
Message-ID: <NBBBIGEGHIGMPCNKHCECMENDEAAA.kenn@bluetree.ie> (raw)
In-Reply-To: <20021107152454.GH5219@pasky.ji.cz>

> Dear diary, on Thu, Nov 07, 2002 at 02:22:45PM CET, I got a letter,
> where Peter Samuelson <peter@cadcamlab.org> told me, that...
> > Remember, the whole point of HOSTCC is to support a build environment
> > different from the compile target - arbitrarily different, even.
> 
> I'm a bit lost here - the kernel uses tons of gcc extensions - 
> how is another
> compiler supposed to understand them? And if it is specifically 
> extended to
> understand them, isn't it likely that it'll understand the 
> -shared switch in
> gcc-like way as well?
> 
> Or better, what other compiler is known to build a kernel than 
> gcc? At least
> anything that doesn't define __GNUC__ should IMHO fail inside of 
> init/main.c.
> And how likely is situation when someone want to configure a kernel with
> non-gcc compiler and actually build it with gcc?

When you're cross-compiling a kernel.

> I thought that the point of HOSTCC is to allow to use a 
> non-standart version
> of gcc for kernel build.

Nope.  It's mainly for cross-compilation.  You want to compile the
kernel itself for your targer architecture, but the compilation tools
need to run on the build machine so need a different compiler.

The gcc/kgcc thing is only a convenient side effect.

Later,
Kenn


  reply	other threads:[~2002-11-07 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 18:52 Petr Baudis
2002-11-06 21:29 ` Sam Ravnborg
2002-11-06 22:03   ` Petr Baudis
2002-11-07 10:00     ` Peter Samuelson
2002-11-07 10:57       ` Roman Zippel
2002-11-07 11:47         ` Peter Samuelson
2002-11-07 12:09           ` Roman Zippel
2002-11-07 12:37             ` Peter Samuelson
2002-11-07 13:04               ` Roman Zippel
2002-11-07 13:22                 ` Peter Samuelson
2002-11-07 13:45                   ` Roman Zippel
2002-11-07 13:59                     ` Peter Samuelson
2002-11-07 15:24                   ` Petr Baudis
2002-11-07 16:20                     ` Kenn Humborg [this message]
2002-11-07 18:52                     ` Peter Samuelson

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=NBBBIGEGHIGMPCNKHCECMENDEAAA.kenn@bluetree.ie \
    --to=kenn@bluetree.ie \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pasky@ucw.cz \
    --cc=peter@cadcamlab.org \
    --cc=zippel@linux-m68k.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®