From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>
Subject: [PATCH v3 2/3] binutils: Package libsframe
Date: Thu, 19 Jan 2023 15:51:40 -0800 [thread overview]
Message-ID: <20230119235141.1603399-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20230119235141.1603399-1-raj.khem@gmail.com>
libsframe is newly added in binutils 2.40
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
v1 -> v2:
- Rebase
v2 -> v3:
- Rebase
meta/recipes-devtools/binutils/binutils_2.40.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/binutils/binutils_2.40.bb b/meta/recipes-devtools/binutils/binutils_2.40.bb
index 67240383f7..9087af87c5 100644
--- a/meta/recipes-devtools/binutils/binutils_2.40.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.40.bb
@@ -66,7 +66,7 @@ PACKAGE_BEFORE_PN += "libbfd libopcodes gprofng"
FILES:libbfd = "${libdir}/libbfd-*.so.* ${libdir}/libbfd-*.so"
FILES:libopcodes = "${libdir}/libopcodes-*.so.* ${libdir}/libopcodes-*.so"
FILES:gprofng = "${sysconfdir}/gprofng.rc ${libdir}/gprofng/libgp-*.so ${libdir}/gprofng/libgprofng.so.* ${bindir}/gp-* ${bindir}/gprofng"
-FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so"
+FILES:${PN}-dev += "${libdir}/gprofng/libgprofng.so ${libdir}/libsframe.so"
SRC_URI:append:class-nativesdk = " file://0003-binutils-nativesdk-Search-for-alternative-ld.so.conf.patch "
USE_ALTERNATIVES_FOR:class-nativesdk = ""
--
2.39.1
next prev parent reply other threads:[~2023-01-19 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 23:51 [PATCH v3 1/3] binutils: Upgrade to 2.40 release Khem Raj
2023-01-19 23:51 ` Khem Raj [this message]
2023-01-19 23:51 ` [PATCH v3 3/3] elfutils: Fix build with libcurl >= 7.87 Khem Raj
2023-01-20 11:47 ` [OE-core] [PATCH v3 1/3] binutils: Upgrade to 2.40 release Luca Ceresoli
2023-01-20 18:11 ` Khem Raj
2023-01-24 8:58 ` Alexandre Belloni
2023-01-25 1:27 ` Khem Raj
2023-02-18 21:56 ` Alexandre Belloni
2023-02-18 21:59 ` Martin Jansa
2023-02-19 0:59 ` 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=20230119235141.1603399-2-raj.khem@gmail.com \
--to=raj.khem@gmail.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