From: "Wang Mingyu" <wangmy@cn.fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@cn.fujitsu.com>
Subject: [OE-core] [PATCH] libusb1: upgrade 1.0.22 -> 1.0.23
Date: Thu, 2 Apr 2020 02:16:58 -0700 [thread overview]
Message-ID: <1585819019-28752-2-git-send-email-wangmy@cn.fujitsu.com> (raw)
In-Reply-To: <1585819019-28752-1-git-send-email-wangmy@cn.fujitsu.com>
no-dll.patch
removed since it is no available for 1.0.23
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../libusb/libusb1/no-dll.patch | 19 -------------------
.../{libusb1_1.0.22.bb => libusb1_1.0.23.bb} | 5 ++---
2 files changed, 2 insertions(+), 22 deletions(-)
delete mode 100644 meta/recipes-support/libusb/libusb1/no-dll.patch
rename meta/recipes-support/libusb/{libusb1_1.0.22.bb => libusb1_1.0.23.bb} (88%)
diff --git a/meta/recipes-support/libusb/libusb1/no-dll.patch b/meta/recipes-support/libusb/libusb1/no-dll.patch
deleted file mode 100644
index 6e6bb83d1f..0000000000
--- a/meta/recipes-support/libusb/libusb1/no-dll.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-As all invokes all-recursive which uses sub-makes to invoke all-am, the
-resulting makefile wants to build libusb-1.0.la twice. In non-parallel builds
-the second attempt is skipped as the target already exists, but in highly
-parallel builds it's likely that two makes will be building libusb-1.0.la at the
-same time.
-
-Solve this by removing the explicit all target, which as libusb-1.0.dll isn't
-built under Linux is redundant anyway.
-
-Upstream-Status: Pending
-Signed-off-by: Ross Burton <ross.burton@intel.com>
-
-diff --git a/libusb/Makefile.am b/libusb/Makefile.am
-index 0cab0a0..c880213 100644
---- a/libusb/Makefile.am
-+++ b/libusb/Makefile.am
-@@ -1,2 +0,0 @@
--all: libusb-1.0.la libusb-1.0.dll
--
diff --git a/meta/recipes-support/libusb/libusb1_1.0.22.bb b/meta/recipes-support/libusb/libusb1_1.0.23.bb
similarity index 88%
rename from meta/recipes-support/libusb/libusb1_1.0.22.bb
rename to meta/recipes-support/libusb/libusb1_1.0.23.bb
index 1d9d772575..2fd658b4ef 100644
--- a/meta/recipes-support/libusb/libusb1_1.0.22.bb
+++ b/meta/recipes-support/libusb/libusb1_1.0.23.bb
@@ -9,12 +9,11 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
BBCLASSEXTEND = "native nativesdk"
SRC_URI = "${SOURCEFORGE_MIRROR}/libusb/libusb-${PV}.tar.bz2 \
- file://no-dll.patch \
file://run-ptest \
"
-SRC_URI[md5sum] = "466267889daead47674df933cea9cacb"
-SRC_URI[sha256sum] = "75aeb9d59a4fdb800d329a545c2e6799f732362193b465ea198f2aa275518157"
+SRC_URI[md5sum] = "be79ed4a4a440169deec8beaac6aae33"
+SRC_URI[sha256sum] = "4fc17b2ef3502757641bf8fe2c14ad86ec86302a2b785abcb0806fd03aa1201f"
S = "${WORKDIR}/libusb-${PV}"
--
2.17.1
next prev parent reply other threads:[~2020-04-02 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 9:16 [OE-core] [PATCH] elfutils: upgrade 0.178 -> 0.179 Wang Mingyu
2020-04-02 9:16 ` Wang Mingyu [this message]
2020-04-02 9:16 ` [OE-core] [PATCH] xserver-xorg: upgrade 1.20.7 -> 1.20.8 Wang Mingyu
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=1585819019-28752-2-git-send-email-wangmy@cn.fujitsu.com \
--to=wangmy@cn.fujitsu.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox