From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libpfm4: bump to version 4.9.0
Date: Sun, 20 May 2018 17:03:02 +0200 [thread overview]
Message-ID: <20180520150302.4205-1-fontaine.fabrice@gmail.com> (raw)
Add hash for license file
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/libpfm4/libpfm4.hash | 7 ++++---
package/libpfm4/libpfm4.mk | 2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/package/libpfm4/libpfm4.hash b/package/libpfm4/libpfm4.hash
index 8bebc493fd..20671fb6e0 100644
--- a/package/libpfm4/libpfm4.hash
+++ b/package/libpfm4/libpfm4.hash
@@ -1,5 +1,6 @@
# From http://sourceforge.net/projects/perfmon2/files/libpfm4/:
-sha1 2ed06d6e746f7b1cd4b70e9736e621052f60d625 libpfm-4.6.0.tar.gz
-md5 5077b9022440e4951d96f2d0e73bd487 libpfm-4.6.0.tar.gz
+sha1 3a7b556e0778fd76e9e7abb06e5d4d2599ffbefc libpfm-4.9.0.tar.gz
+md5 42ad4a2e5b8e1f015310db8535739c73 libpfm-4.9.0.tar.gz
# Locally calculated
-sha256 5ab1e5b0472550f9037a8800834f6bc3b927690070f69fac0b67284b4b05fd5f libpfm-4.6.0.tar.gz
+sha256 db0fbe8ee28fd9beeb5d3e80b7cb3b104debcf6a9fcf5cb8b882f0662c79e4e2 libpfm-4.9.0.tar.gz
+sha256 beef323d68fc5db9c67b20e8e9de7ccde371d20cdbcdd686804055b18b926d90 COPYING
diff --git a/package/libpfm4/libpfm4.mk b/package/libpfm4/libpfm4.mk
index 913fc35831..88632f478b 100644
--- a/package/libpfm4/libpfm4.mk
+++ b/package/libpfm4/libpfm4.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBPFM4_VERSION = 4.6.0
+LIBPFM4_VERSION = 4.9.0
LIBPFM4_SOURCE = libpfm-$(LIBPFM4_VERSION).tar.gz
LIBPFM4_SITE = http://downloads.sourceforge.net/project/perfmon2/libpfm4
LIBPFM4_LICENSE = libpfm4 license
--
2.14.1
next reply other threads:[~2018-05-20 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 15:03 Fabrice Fontaine [this message]
2018-05-20 16:45 ` [Buildroot] [PATCH 1/1] libpfm4: bump to version 4.9.0 Thomas Petazzoni
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=20180520150302.4205-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@busybox.net \
/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