All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Paul Bame <bame@fc.hp.com>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Another possible linker problem
Date: Thu, 06 Jul 2000 17:16:07 -0600	[thread overview]
Message-ID: <13488.962925367@upchuck> (raw)
In-Reply-To: Your message of Fri, 07 Jul 2000 09:06:26 +1000. <Pine.LNX.4.21.0007070848540.12175-100000@front.linuxcare.com.au>


  In message <Pine.LNX.4.21.0007070848540.12175-100000@front.linuxcare.com.au>y
ou write:
  > [cc to list in case others have the same problem.]
  > I reckon this error is probably fixed by the patch I checked in last
  > night.  elf32_hppa_size_stubs had this code in it
  > 
  > 		      if (hash->root.type == bfd_link_hash_undefined
  > 			  || hash->root.type == bfd_link_hash_undefweak)
  > 			continue;
  > 
  > 		      while (hash->root.type == bfd_link_hash_indirect
  > 			     || hash->root.type == bfd_link_hash_warning)
  > 			hash = (struct elf_link_hash_entry *)
  > 			  hash->root.u.i.link;
  > 
  > and the problem is that we may have an indirect symbol (results from
  > symbol versioning) pointing to an undefined symbol.  The simple fix is to
  > traverse the indirect links before checking for undefined syms.
Yea, I don't think I ever implemented indirects in the PA tools.  I suspect
there's other PA code that doesn't handle them correctly.

I'm glad to see someone making the right things happen with that old crusty
code.


jeff

      reply	other threads:[~2000-07-06 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E13AEnD-0000ju-00@noam.fc.hp.com>
2000-07-06 23:06 ` [parisc-linux] Another possible linker problem Alan Modra
2000-07-06 23:16   ` Jeffrey A Law [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=13488.962925367@upchuck \
    --to=law@cygnus.com \
    --cc=alan@linuxcare.com.au \
    --cc=bame@fc.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    /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.