This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: php5: probably binutils bug

Michael sent me this testcase showing a linker bug, cunningly claiming
it was a powerpc64le failure.  I tried at first to shirk all
responsibility since I didn't reproduce the problem.  He wouldn't let
that go, pointing out that I simply had to add -Wl,--as-needed.  Oh
well, let's have a look then..  Hey!  It's a generic problem!

Here's the testcase, showing the failure on x64_64-linux using a 2.24
linker.  It's a little nasty in that isn't linked against, but we do allow shared libraries to be built with undefined

cat > libx.c <<EOF
extern void pam_end (void);
void dumpme (void)
  pam_end ();
cat > liby.c <<EOF
extern void pam_end (void);
void pam_end (void) {}
cat > appx.c <<EOF
extern void dumpme (void);
int main (void)
  return 0;
cat > liby.ver <<EOF
  global: pam_end;
  local: *;
gcc -fPIC -shared -o libx.c
gcc -fPIC -shared -o liby.c -Wl,--version-script,liby.ver
ln -s ~/build/gas-virgin/x86_64-linux/ld/ld-new ld
gcc -B. -o appx appx.c -L. -Wl,--as-needed -lx -ly
./ undefined reference to `pam_end'
collect2: ld returned 1 exit status

What's happening is that isn't being seen as needed in appx,
because the reference in is to an unversioned symbol while provides a versioned symbol.  Fixed as follows.

	* elf64-ppc.c (_bfd_elf_add_default_symbol): Set dynamic_def
	and ref_dynamic_nonweak when chaining together indirect

diff --git a/bfd/elflink.c b/bfd/elflink.c
index 1e6abd9..6fa62f9 100644
--- a/bfd/elflink.c
+++ b/bfd/elflink.c
@@ -1702,6 +1702,12 @@ _bfd_elf_add_default_symbol (bfd *abfd,
       ht = (struct elf_link_hash_entry *) hi->;
       (*bed->elf_backend_copy_indirect_symbol) (info, ht, hi);
+      /* A reference to the SHORTNAME symbol from a dynamic library
+	 will be satisfied by the versioned symbol at runtime.  In
+	 effect, we have a reference to the versioned symbol.  */
+      ht->ref_dynamic_nonweak |= hi->ref_dynamic_nonweak;
+      hi->dynamic_def |= ht->dynamic_def;
       /* See if the new flags lead us to realize that the symbol must
 	 be dynamic.  */
       if (! *dynsym)
@@ -1771,6 +1777,8 @@ nondefault:
       if (hi->root.type == bfd_link_hash_indirect)
 	  (*bed->elf_backend_copy_indirect_symbol) (info, h, hi);
+	  h->ref_dynamic_nonweak |= hi->ref_dynamic_nonweak;
+	  hi->dynamic_def |= h->dynamic_def;
 	  /* See if the new flags lead us to realize that the symbol
 	     must be dynamic.  */

Alan Modra
Australia Development Lab, IBM

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]