From: Philip Blundell <pb@nexus.co.uk>
To: sbambrough@storm.ca
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: [Fwd: Memory violation in init on ARM Linux. in glibc mainline...]
Date: Mon, 30 Sep 2002 14:27:00 -0000 [thread overview]
Message-ID: <1033421269.30796.3.camel@kc> (raw)
In-Reply-To: <3D98848F.6000308@redhat.com>
On Mon, 2002-09-30 at 18:06, Ulrich Drepper wrote:
> I'm trying to build glibc on my NetWinder and am running into a memory
> violation in glibc when running rpcgen during the build of the others
> target in the sunrpc directory.
I think this is a binutils bug. From what I remember, the relocation
information gets scrunged somehow when -z combreloc is enabled, so none
of the GOT entries are actually relocated properly at run time.
I have some BFD patches somewhere to implement reference counting
properly, which seemed to help with that. I can send you a copy if you
want, but I'm not sure if they will still apply against the latest
sources.
p.
next prev parent reply other threads:[~2002-09-30 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 10:06 Ulrich Drepper
2002-09-30 14:27 ` Philip Blundell [this message]
[not found] ` <1033488496.3501.2.camel@pauli>
2002-10-01 9:59 ` Philip Blundell
2002-10-01 12:29 ` Roland McGrath
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=1033421269.30796.3.camel@kc \
--to=pb@nexus.co.uk \
--cc=libc-hacker@sources.redhat.com \
--cc=sbambrough@storm.ca \
/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).