From: "Jeremy Puhlman" <jpuhlman@mvista.com>
To: openembedded-core@lists.openembedded.org
Cc: Jeremy Puhlman <jpuhlman@mvista.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: [dunfell][PATCH 3/3] buildtools-extended-tarball: Add libstc++.a
Date: Sun, 26 Apr 2020 12:13:02 -0700 [thread overview]
Message-ID: <20200426191302.25782-3-jpuhlman@mvista.com> (raw)
In-Reply-To: <20200426191302.25782-1-jpuhlman@mvista.com>
From: Jeremy Puhlman <jpuhlman@mvista.com>
Builds like native-openjdk, really wants a to link
some tools against the static version. Since when
using the extended tarball, its the only place to
get it, add the library.
(From OE-Core rev: 59c4a3fdbbfd5a6aaba7e0a1675dcd5866a7f3a4)
Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta/recipes-core/meta/buildtools-extended-tarball.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/meta/buildtools-extended-tarball.bb b/meta/recipes-core/meta/buildtools-extended-tarball.bb
index dd780c5d57..e38967af3f 100644
--- a/meta/recipes-core/meta/buildtools-extended-tarball.bb
+++ b/meta/recipes-core/meta/buildtools-extended-tarball.bb
@@ -23,6 +23,7 @@ TOOLCHAIN_HOST_TASK += "\
nativesdk-libgcc \
nativesdk-libstdc++ \
nativesdk-libstdc++-dev \
+ nativesdk-libstdc++-staticdev \
nativesdk-libtool \
nativesdk-pkgconfig \
nativesdk-glibc-utils \
--
2.20.1
next prev parent reply other threads:[~2020-04-26 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 19:13 [dunfell][PATCH 1/3] qemu-system-native: Fix commented out PACKAGECONFIG Jeremy Puhlman
2020-04-26 19:13 ` [dunfell][PATCH 2/3] nativesdk-gcc-runtime: enable building libstdc++.a Jeremy Puhlman
2020-04-26 19:13 ` Jeremy Puhlman [this message]
2020-04-27 21:28 ` [OE-core] [dunfell][PATCH 1/3] qemu-system-native: Fix commented out PACKAGECONFIG Steve Sakoman
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=20200426191302.25782-3-jpuhlman@mvista.com \
--to=jpuhlman@mvista.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.