public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: Hi Andrew
Date: Wed, 14 Apr 2010 07:30:51 +0000	[thread overview]
Message-ID: <4BC56F2B.1000207@codesourcery.com> (raw)
In-Reply-To: <201004140908.16136.fabio.giovagnini@aurion-tech.com>

On 14/04/10 08:08, Fabio Giovagnini wrote:
> Ok. so the Makefile for zImage needs to be modified to use the libc functions
> embedded into the kernel source tree. Is it right?
> If yes, how is it possible to have a general coccect behaviour?

I'm sorry, I'm not sure I understand the question.

Yes, the makefile needs to be modified to remove the dependency on 
libgcc. This was done for the kernel itself a few versions ago. It means 
that the toolchain does not need any special configuration to build the 
kernel, in cases like this where the usermode compiler is incompatible 
with the kernel.

If you're asking how to do the modification, I don't know. I'm not a 
kernel hacker.

If you're asking how any hypothetical project should handle this, then 
the answer is that they should rely on the toolchain, and not have to 
worry about it. The kernel is special - it is traditionally compiled 
with a toolchain unsuitable for building bare-metal programs. It is 
desirable that the same compiler is used for user mode, and for the 
kernel, because having a whole separate toolchain would be a lot of 
wasted effort, but it means that the kernel makefiles have to work hard 
to reconfigure the tools using custom parameters, linker scripts and 
overriding compiler built-ins.

Is that the answer to the question you were asking?

Andrew

  reply	other threads:[~2010-04-14  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14  7:08 Hi Andrew Fabio Giovagnini
2010-04-14  7:30 ` Andrew Stubbs [this message]
2010-04-14  8:22 ` Fabio Giovagnini

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=4BC56F2B.1000207@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=linux-sh@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