From: jon@ringle.org
To: ptxdist@pengutronix.de
Cc: Jon Ringle <jringle@gridpoint.com>
Subject: [ptxdist] [PATCH v2] libelf: version bump 0.170 -> 0.171
Date: Tue, 5 Jun 2018 14:25:59 -0400 [thread overview]
Message-ID: <1528223160-9037-1-git-send-email-jon@ringle.org> (raw)
From: Jon Ringle <jringle@gridpoint.com>
Signed-off-by: Jon Ringle <jringle@gridpoint.com>
---
...error-as-it-tends-to-break-with-new-gcc-ver.patch | 20 --------------------
patches/elfutils-0.170/autogen.sh | 1 -
patches/elfutils-0.170/series | 4 ----
rules/libelf.make | 4 ++--
4 files changed, 2 insertions(+), 27 deletions(-)
delete mode 100644 patches/elfutils-0.170/0001-disable-Werror-as-it-tends-to-break-with-new-gcc-ver.patch
delete mode 120000 patches/elfutils-0.170/autogen.sh
delete mode 100644 patches/elfutils-0.170/series
diff --git a/patches/elfutils-0.170/0001-disable-Werror-as-it-tends-to-break-with-new-gcc-ver.patch b/patches/elfutils-0.170/0001-disable-Werror-as-it-tends-to-break-with-new-gcc-ver.patch
deleted file mode 100644
index ed336e4..0000000
--- a/patches/elfutils-0.170/0001-disable-Werror-as-it-tends-to-break-with-new-gcc-ver.patch
+++ /dev/null
@@ -1,20 +0,0 @@
-From: Helmut Grohne <helmut@subdivi.de>
-Date: Mon, 7 May 2018 02:42:31 +0200
-Subject: [PATCH] disable -Werror as it tends to break with new gcc versions
-
----
- config/eu.am | 1 -
- 1 file changed, 1 deletion(-)
-
-diff --git a/config/eu.am b/config/eu.am
-index 8fe1e259f9e2..c5a6209a4e04 100644
---- a/config/eu.am
-+++ b/config/eu.am
-@@ -71,7 +71,6 @@ AM_CFLAGS = -std=gnu99 -Wall -Wshadow -Wformat=2 \
- -Wold-style-definition -Wstrict-prototypes \
- $(LOGICAL_OP_WARNING) $(DUPLICATED_COND_WARNING) \
- $(NULL_DEREFERENCE_WARNING) $(IMPLICIT_FALLTHROUGH_WARNING) \
-- $(if $($(*F)_no_Werror),,-Werror) \
- $(if $($(*F)_no_Wunused),,-Wunused -Wextra) \
- $(if $($(*F)_no_Wstack_usage),,$(STACK_USAGE_WARNING)) \
- $($(*F)_CFLAGS)
diff --git a/patches/elfutils-0.170/autogen.sh b/patches/elfutils-0.170/autogen.sh
deleted file mode 120000
index 9f8a4cb..0000000
--- a/patches/elfutils-0.170/autogen.sh
+++ /dev/null
@@ -1 +0,0 @@
-../autogen.sh
\ No newline at end of file
diff --git a/patches/elfutils-0.170/series b/patches/elfutils-0.170/series
deleted file mode 100644
index 6e83826..0000000
--- a/patches/elfutils-0.170/series
+++ /dev/null
@@ -1,4 +0,0 @@
-# generated by git-ptx-patches
-#tag:base --start-number 1
-0001-disable-Werror-as-it-tends-to-break-with-new-gcc-ver.patch
-# 881dc427356ca2d007dd3d3f576ea5a8 - git-ptx-patches magic
diff --git a/rules/libelf.make b/rules/libelf.make
index 4846563..74177c6 100644
--- a/rules/libelf.make
+++ b/rules/libelf.make
@@ -17,8 +17,8 @@ PACKAGES-$(PTXCONF_LIBELF) += libelf
#
# Paths and names
#
-LIBELF_VERSION := 0.170
-LIBELF_MD5 := 03599aee98c9b726c7a732a2dd0245d5
+LIBELF_VERSION := 0.171
+LIBELF_MD5 := 3926422984f02a2e5f7242d22ab6e1fa
LIBELF := elfutils-$(LIBELF_VERSION)
LIBELF_SUFFIX := tar.bz2
LIBELF_URL := https://sourceware.org/elfutils/ftp/$(LIBELF_VERSION)/$(LIBELF).$(LIBELF_SUFFIX)
--
1.9.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-06-05 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 18:25 jon [this message]
2018-06-05 18:26 ` [ptxdist] [PATCH 1/2] systemd: upstream patch: add __nr_statx defines for extra architectures jon
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=1528223160-9037-1-git-send-email-jon@ringle.org \
--to=jon@ringle.org \
--cc=jringle@gridpoint.com \
--cc=ptxdist@pengutronix.de \
/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