From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 0f54968346962ab9b1fed900db53a6c896f13176
Date: Fri, 29 Jun 2012 17:53:18 +0200 [thread overview]
Message-ID: <20120629155319.C2C0620352@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 3.x development tree".
The branch, master has been updated
via 0f54968346962ab9b1fed900db53a6c896f13176 (commit)
from 2d6fd519f945bcd2a10b8ffd5f00dee4385dc137 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 0f54968346962ab9b1fed900db53a6c896f13176
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Jun 29 17:51:52 2012 +0200
binutils: Fix assert error in ld.
http://sourceware.org/bugzilla/show_bug.cgi?id=14189
Fixes #10073.
-----------------------------------------------------------------------
Summary of changes:
binutils/binutils.nm | 2 +-
.../patches/binutils-2.22.52.0.4-refcount.patch0 | 19 +++++++++++++++++++
2 files changed, 20 insertions(+), 1 deletions(-)
create mode 100644 binutils/patches/binutils-2.22.52.0.4-refcount.patch0
Difference in files:
diff --git a/binutils/binutils.nm b/binutils/binutils.nm
index e03ac50..b5c2c48 100644
--- a/binutils/binutils.nm
+++ b/binutils/binutils.nm
@@ -5,7 +5,7 @@
name = binutils
version = 2.22.52.0.4
-release = 1
+release = 2
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = Development/Tools
diff --git a/binutils/patches/binutils-2.22.52.0.4-refcount.patch0 b/binutils/patches/binutils-2.22.52.0.4-refcount.patch0
new file mode 100644
index 0000000..33fcfd4
--- /dev/null
+++ b/binutils/patches/binutils-2.22.52.0.4-refcount.patch0
@@ -0,0 +1,19 @@
+http://sourceware.org/bugzilla/show_bug.cgi?id=14189
+
+Index: bfd/elf32-arm.c
+===================================================================
+RCS file: /cvs/src/src/bfd/elf32-arm.c,v
+retrieving revision 1.294
+diff -u -3 -p -r1.294 elf32-arm.c
+--- bfd/elf32-arm.c 28 Jun 2012 16:57:24 -0000 1.294
++++ bfd/elf32-arm.c 29 Jun 2012 13:21:52 -0000
+@@ -12668,7 +12668,8 @@ elf32_arm_check_relocs (bfd *abfd, struc
+
+ /* If the symbol is a function that doesn't bind locally,
+ this relocation will need a PLT entry. */
+- root_plt->refcount += 1;
++ if (root_plt->refcount != -1)
++ root_plt->refcount += 1;
+
+ if (!call_reloc_p)
+ arm_plt->noncall_refcount++;
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-06-29 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120629155319.C2C0620352@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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