From: Andrew Stubbs <ams@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: objdump on libgcc
Date: Thu, 01 Apr 2010 07:59:11 +0000 [thread overview]
Message-ID: <4BB4524F.9060706@codesourcery.com> (raw)
In-Reply-To: <201004010937.26235.fabio.giovagnini@aurion-tech.com>
On 01/04/10 08:37, Fabio Giovagnini wrote:
> This is the result,
> so I think libgcc is only for fdpic target, so if I need it for building
> kernel (and for making zImage it seems to be essential) I can link only a
> wrong libgcc.
Absolutely, there is only FDPIC libgcc in the release I sent to you.
The kernel has not needed glibc for a while now. The relevant routines
were copied/rewritten to arch/sh/lib.
I expect that all the routines you need are present, so it should just
be makefile adjustments. If it does need something extra (that somehow
the whole of the rest of the kernel can do without) then I expect it can
be extracted from the compiler sources (gcc/config/sh/lib1funcs.asm).
The linker should have already told you this list of routines it needs.
Andrew
prev parent reply other threads:[~2010-04-01 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 7:37 objdump on libgcc Fabio Giovagnini
2010-04-01 7:59 ` Andrew Stubbs [this message]
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=4BB4524F.9060706@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;
as well as URLs for NNTP newsgroup(s).