From: Daniel Jacobowitz <drow@false.org>
To: gcc@gcc.gnu.org, binutils@sources.redhat.com
Subject: Re: RFH: libgcc_s.so being unnecessarily linked for mipsel-linux crosscompiler...
Date: Fri, 29 Jul 2005 03:20:00 -0000 [thread overview]
Message-ID: <20050729032029.GA12838@nevyn.them.org> (raw)
In-Reply-To: <42E996FD.1000208@avtrex.com>
On Thu, Jul 28, 2005 at 07:39:57PM -0700, David Daney wrote:
> It seems that the linker thinks that any shared object that references
> the magic _gp_disp symbol actually provides it. Since all mips objects
> reference _gp_disp, ld thinks that all shared objects are required to
> resolve all the other _gp_disp references. This causes all shared
> objects specified with --as-needed to be deemed needed and get a
> DT_NEEDED entry.
>
> The linker automagically resolves _gp_disp so this symbol should not
> cause a shared library to be needed.
>
> I hope that makes at least a little sense.
>
> I suspect that the problem is mips specific as _gp_disp handling is mips
> specific.
Yes, you're probably right. I thought this sounded familiar, but
couldn't find any references.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-29 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 1:07 dank
2005-07-29 2:40 ` David Daney
2005-07-29 3:20 ` Daniel Jacobowitz [this message]
2005-07-29 3:36 ` David Daney
2005-07-29 5:53 ` Alan Modra
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=20050729032029.GA12838@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).