From: Carlos O'Donell <carlos@systemhalted.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Getting PIE to work (was How to reclaim .rela.dyn entries for symbols that become hidden?)
Date: Thu, 7 Jul 2005 23:23:18 -0400 [thread overview]
Message-ID: <20050708032318.GC5314@systemhalted.org> (raw)
In-Reply-To: <200507072200.10597.vapier@gentoo.org>
On Thu, Jul 07, 2005 at 10:00:10PM -0400, Mike Frysinger wrote:
> On Thursday 07 July 2005 09:56 pm, Randolph Chung wrote:
> > > does that mean you're looking into fixing PIE on parisc ? we noticed in
> > > Gentoo that nscd fails to run since glibc forces it to either be built as
> > > a PIE or not at all:
> > > root@mindcircus 0 ~ # nscd
> > > nscd: error while loading shared libraries: unexpected reloc type 0x42
> > >
> > > building anything as PIE fails due to this reloc ... looks like binutils
> > > generates relocs of type R_PARISC_PLABEL14 and R_PARISC_PLABEL21 but
> > > glibc only knows how to handle R_PARISC_PLABEL32 ...
> >
> > palinux glibc cvs has patch to do this. We'll propagate this upstream.
>
> ah, was not aware parisc kept a glibc cvs tree
>
> thanks for the great news :)
We haven't pulled from upstream since 2005-06-08. We are trying to get a
working TLS build :)
c.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2005-07-08 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050630165918.GG5269@systemhalted.org>
2005-07-07 21:59 ` [parisc-linux] Getting PIE to work (was How to reclaim .rela.dyn entries for symbols that become hidden?) Mike Frysinger
2005-07-08 1:56 ` Randolph Chung
2005-07-08 2:00 ` Mike Frysinger
2005-07-08 2:06 ` Randolph Chung
2005-07-08 3:23 ` Carlos O'Donell [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=20050708032318.GC5314@systemhalted.org \
--to=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=vapier@gentoo.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