From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Cc: amodra@one.net.au
Subject: Re: [parisc-linux] elflink.h (elf_bfd_final_link)
Date: Mon, 28 May 2001 14:51:09 +0100 [thread overview]
Message-ID: <20010528145109.A25745@linuxcare.com> (raw)
In-Reply-To: <20010528184653.B11349@squeak.one.net.au>; from amodra@one.net.au on Mon, May 28, 2001 at 06:46:53PM +0930
On Mon, May 28, 2001 at 06:46:53PM +0930, amodra@one.net.au wrote:
> Not calling elf_link_output_extsym has the effect that the back-end
> finish_dynamic_symbol routine isn't called, which means various hacks
> are needed like the following:
I built a new binutils from pehc:~amodra/binutils-current, which has
this patch, and it produces a working find and make.
So, we need a new binutils, and a check for more broken binaries.
This check seems to do it, someone can roll it in to plt-checker.
for i in /bin/* /sbin/* /usr/bin/* /usr/sbin/*; do if readelf -r $i 2> /dev/null | grep -q R_PARISC_NONE; then echo ===== $i =====; fi; done
Things I know have a problem are find, make, modutils. libmagick++5
has also been reported. However, I don't have much installed, so
someone need to run the check over the archive, I guess.
I still have an issue with the binaries produced from a modutils
build though (e.g depmod), which still have a R_PARISC_NONE in
them. I've tar-ed up my build tree, as pehc:~rhirst/modutilsbug.tgz
The libc, etc are as per the ones in findbug.tgz. The binaries do
seem to work, but Alan says R_PARISC_NONE is indicative of a linker
bug.
Many thanks to Alan for his help!
Richard
prev parent reply other threads:[~2001-05-28 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 9:16 [parisc-linux] elflink.h (elf_bfd_final_link) amodra
2001-05-28 13:51 ` Richard Hirst [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=20010528145109.A25745@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=amodra@one.net.au \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.