From: Daniel Jacobowitz <drow@false.org>
To: "Peter S. Mazinger" <ps.m@gmx.net>
Cc: binutils@sources.redhat.com
Subject: Re: binutils 2.15 / gcc-3.3.5 (3.4.3) produce text relocations on arm
Date: Tue, 04 Jan 2005 18:35:00 -0000 [thread overview]
Message-ID: <20050104183529.GA15976@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0501041813210.5384-200000@lnx.bridge.intra>
On Tue, Jan 04, 2005 at 06:16:56PM +0100, Peter S. Mazinger wrote:
> On Tue, 4 Jan 2005, Daniel Jacobowitz wrote:
>
> > On Tue, Jan 04, 2005 at 04:25:26PM +0100, Peter S. Mazinger wrote:
> > > Hello!
> > >
> > > I have tried some versions of binutils-2.15 (up to and including
> > > 2.15.94.0.2) in conjunction w/ gcc-3.3.5 and gcc-3.4.3, all combinations
> > > produce text relocations on x86 (using glibc / uclibc) in shared libs.
> > > Can't tell if gcc or binutils produce this, maybe a linker script?
> > >
> > > Please CC to me, thanks Peter
> >
> > Have you checked whether you are actually producing text relocations,
> > or just setting DT_TEXTREL? I just encountered another binutils ARM
> > bug which set DT_TEXTREL incorrectly.
>
> I have checked: readelf -d file | grep TEXT
Then could you check whether any of the relocations are actually in the
text segment?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2005-01-04 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0501041617290.874-100000@lnx.bridge.intra>
2005-01-04 16:48 ` Daniel Jacobowitz
2005-01-04 17:17 ` Peter S. Mazinger
2005-01-04 18:35 ` Daniel Jacobowitz [this message]
2005-01-05 6:58 ` Peter S. Mazinger
2005-03-14 11:44 ` Peter S. Mazinger
2005-03-18 23:52 ` PATCH for " Daniel Jacobowitz
2005-03-19 1:23 ` Peter S. Mazinger
2005-04-04 13:52 ` Richard Earnshaw
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=20050104183529.GA15976@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=ps.m@gmx.net \
/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).