From: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-oe][PATCH] ccid: upgrade 1.4.30 -> 1.4.31
Date: Wed, 6 Nov 2019 20:10:09 +0800 [thread overview]
Message-ID: <1573042209-43148-1-git-send-email-zhengrq.fnst@cn.fujitsu.com> (raw)
1) Add 0001-Add-build-rule-for-README.patch to fix do_configure error:
Makefile.am: required file `./README' not found
Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
---
.../ccid/ccid/0001-Add-build-rule-for-README.patch | 22 ++++++++++++++++++++++
.../ccid/{ccid_1.4.30.bb => ccid_1.4.31.bb} | 5 +++--
2 files changed, 25 insertions(+), 2 deletions(-)
create mode 100644 meta-oe/recipes-support/ccid/ccid/0001-Add-build-rule-for-README.patch
rename meta-oe/recipes-support/ccid/{ccid_1.4.30.bb => ccid_1.4.31.bb} (71%)
diff --git a/meta-oe/recipes-support/ccid/ccid/0001-Add-build-rule-for-README.patch b/meta-oe/recipes-support/ccid/ccid/0001-Add-build-rule-for-README.patch
new file mode 100644
index 0000000..586ff18
--- /dev/null
+++ b/meta-oe/recipes-support/ccid/ccid/0001-Add-build-rule-for-README.patch
@@ -0,0 +1,22 @@
+Subject: [PATCH] Add build rule for README.
+
+fix do_configure error:
+Makefile.am: required file `./README' not found
+
+Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
+---
+ Makefile.am | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/Makefile.am b/Makefile.am
+index 49574a3..a5a7c2a 100644
+--- a/Makefile.am
++++ b/Makefile.am
+@@ -26,3 +26,4 @@ libtool: $(LIBTOOL_DEPS)
+ ChangeLog:
+ git log --stat --decorate=short > $@
+
++README: README.md
+--
+2.7.4
+
diff --git a/meta-oe/recipes-support/ccid/ccid_1.4.30.bb b/meta-oe/recipes-support/ccid/ccid_1.4.31.bb
similarity index 71%
rename from meta-oe/recipes-support/ccid/ccid_1.4.30.bb
rename to meta-oe/recipes-support/ccid/ccid_1.4.31.bb
index 95a41d2..de07bfd 100644
--- a/meta-oe/recipes-support/ccid/ccid_1.4.30.bb
+++ b/meta-oe/recipes-support/ccid/ccid_1.4.31.bb
@@ -8,10 +8,11 @@ RDEPENDS_${PN} = "pcsc-lite"
SRC_URI = "https://ccid.apdu.fr/files/ccid-${PV}.tar.bz2 \
file://no-dep-on-libfl.patch \
+ file://0001-Add-build-rule-for-README.patch \
"
-SRC_URI[md5sum] = "817abceef715e02cb47617621fe192e0"
-SRC_URI[sha256sum] = "ac17087be08880a0cdf99a8a2799a4ef004dc6ffa08b4d9b0ad995f39a53ff7c"
+SRC_URI[md5sum] = "e4690f3362f95adb2332fd47a2b08212"
+SRC_URI[sha256sum] = "6b48d7b6e4390e038d25630f8664fe81618ab00f232d6efbe0e3cc6df28ce8f7"
inherit autotools pkgconfig
--
2.7.4
next reply other threads:[~2019-11-06 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:10 Zheng Ruoqin [this message]
2019-11-06 17:42 ` [meta-oe][PATCH] ccid: upgrade 1.4.30 -> 1.4.31 Khem Raj
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=1573042209-43148-1-git-send-email-zhengrq.fnst@cn.fujitsu.com \
--to=zhengrq.fnst@cn.fujitsu.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.