This is an automated email from the git hooks/post-receive script.

sthibault pushed a commit to branch sid
in repository glibc.

commit 8e5856c18cf268757b0a474e98cab6504812e45f
Author: Samuel Thibault <[email protected]>
Date:   Sun May 29 22:39:00 2016 +0000

    sysdeps/hurd-i386.mk: Work around binutils bug with ifunc relocation 
assertion.
---
 debian/changelog            |  4 ++++
 debian/sysdeps/hurd-i386.mk | 15 +++++++++++++++
 2 files changed, 19 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 61ff4bb..5c35aa3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,10 @@ glibc (2.22-10) UNRELEASED; urgency=medium
     dpkg-dev (>= 1.18.7) as the cputable file is in dpkg, not dpkg-dev.
     Closes: #824127.
 
+  [ Samuel Thibault ]
+  * debian/sysdeps/hurd-i386.mk: Work around binutils bug with ifunc relocation
+    assertion.
+
  -- Aurelien Jarno <[email protected]>  Thu, 12 May 2016 18:06:35 +0200
 
 glibc (2.22-9) unstable; urgency=medium
diff --git a/debian/sysdeps/hurd-i386.mk b/debian/sysdeps/hurd-i386.mk
index d5e72ee..47e34df 100644
--- a/debian/sysdeps/hurd-i386.mk
+++ b/debian/sysdeps/hurd-i386.mk
@@ -12,3 +12,18 @@
 #      debian/libc0.3-dev/$(libdir)/xen
 #endef
 #endif
+
+# FIXME: We are having linking issues with ifunc...
+#
+# when linking libc_pic.os into libc.so:
+# /usr/bin/ld: /tmp/glibc-2.22/build-tree/hurd-i386-libc/libc_pic.os: warning: 
relocation against `_hurd_self_sigstate' in readonly section `.text'
+# /usr/bin/ld: read-only segment has dynamic IFUNC relocations; recompile with 
-fPIC
+# /usr/bin/ld: failed to set dynamic section sizes: Bad value
+# See
+# https://sourceware.org/bugzilla/show_bug.cgi?id=18801
+# https://sourceware.org/ml/libc-alpha/2016-05/msg00686.html
+# https://sourceware.org/bugzilla/show_bug.cgi?id=19939
+# supposed to be fixed in binutils 2.27
+#
+# For now we are just disabling ifunc:
+export libc_cv_ld_gnu_indirect_function=no

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-glibc/glibc.git

Reply via email to