Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: parisc-linux@lists.parisc-linux.org, randolph@tausq.org
Subject: Re: [parisc-linux] Re: Fix for hppa-linux ld.so with newer binutils
Date: Sat, 20 Oct 2001 11:01:23 -0400	[thread overview]
Message-ID: <20011020110123.M10952@visi.net> (raw)
In-Reply-To: <20011021000443.H1037@bubble.sa.bigpond.net.au>

On Sun, Oct 21, 2001 at 12:04:44AM +0930, Alan Modra wrote:
> On Sat, Oct 20, 2001 at 09:54:06AM -0400, Ben Collins wrote:
> > On Sat, Oct 20, 2001 at 05:09:07PM +0930, Alan Modra wrote:
> > > 	* sysdeps/hppa/dl-machine.h (elf_machine_dynamic):  Make it a
> > > 	const function.  Do not use &_DYNAMIC as .got entries for global
> > > 	syms are no longer initialised.  Instead they rely on the reloc,
> > > 	which hasn't yet been applied.
> > > 	(elf_machine_load_address): Make it const.  Call
> > > 	elf_machine_dynamic as that function is called fropm rtld anyway.
> > 
> > Is this the fix for a newly built ld.so segfaulting? If so, there seems
> > to be something else wrong too. Newly built ld.so still segfaults,
> > here's the gdb:
> 
> alan@tea:~$ /lib/ld.so.1 
> Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
> You have invoked `ld.so', the helper program for shared library executables.
> [snip]
> 
> no problems here.
> 
> sourceware CVS binutils as of a few minutes ago, debian glibc-2.2.4-3
> with willy's patch (ftp://ftp.parisc-linux.org/patches/glibc22-hppa.dpatch)
> + mine, gcc from pehc 3.0.2 20010829.
> 
> So, I'm using a newer binutils but older gcc.  The old gcc was an
> accident - I'll try again with something more recent.  binutils, gcc and
> glibc freshly built on an x86-linux system, first building xtools then
> native ones.

The binutils may be the difference. I think Randolph said there was a
patch in CVS that was needed. I'll wait and see if that new package
works.

-- 
 .----------=======-=-======-=========-----------=====------------=-=-----.
/                   Ben Collins    --    Debian GNU/Linux                  \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'

  reply	other threads:[~2001-10-20 15:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20  7:39 [parisc-linux] Fix for hppa-linux ld.so with newer binutils Alan Modra
2001-10-20 13:54 ` [parisc-linux] " Ben Collins
2001-10-20 14:34   ` Alan Modra
2001-10-20 15:01     ` Ben Collins [this message]
2001-10-24 23:51       ` Ben Collins
2001-10-25  0:56         ` Randolph Chung
2001-10-25  1:12           ` Ben Collins
2001-10-25 15:07         ` Matthew Wilcox
2001-10-25 15:50           ` Ben Collins
2001-10-22  3:44     ` Alan Modra
2001-10-20 18:01 ` [parisc-linux] " Carlos O'Donell Jr.
2001-10-21 11:20   ` Alan Modra
2001-10-22 14:05 ` [parisc-linux] " Alan Modra
2001-10-22 16:04   ` Carlos O'Donell Jr.
2001-10-22 16:11     ` Alan Modra
2001-10-23  1:31   ` Ben Collins
2001-10-23  1:59     ` Randolph Chung

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=20011020110123.M10952@visi.net \
    --to=bcollins@debian.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=randolph@tausq.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