From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Fixes found with master versions of clang/gcc
Date: Thu, 23 Jan 2020 12:00:29 -0800 [thread overview]
Message-ID: <cover.1579809439.git.raj.khem@gmail.com> (raw)
libucontext is library implementation for ucontext APIs which in case of
glibc are bundled into C library but not for musl, this helps compiling
apps needing these APIs on musl, e.g. chromium
The following changes since commit ca3993cc4b13d4e661228cee6fb9448adfd0a4ba:
bitbake: tests/fetch: Allow wget upgrade tests to run against a local server (2020-01-22 15:56:39 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/poky-contrib kraj/pu
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=kraj/pu
Khem Raj (4):
perf: Pass LDSHARED and CCLD via EXTRA_OEMAKE
ruby: Remove __has_include and __has_include_next from preprocessed
header file
nss: Pass NSS_USE_ARM_HW_CRYPTO as define in CFLAGS
libucontext: Add recipe
.../0001-pass-LDFLAGS-to-link-step.patch | 31 ++++++++++
meta/recipes-core/musl/libucontext_git.bb | 62 +++++++++++++++++++
meta/recipes-devtools/ruby/ruby.inc | 7 +++
meta/recipes-kernel/perf/perf.bb | 2 +
...figure-option-to-disable-ARM-HW-cryp.patch | 25 ++++++--
5 files changed, 123 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-core/musl/libucontext/0001-pass-LDFLAGS-to-link-step.patch
create mode 100644 meta/recipes-core/musl/libucontext_git.bb
--
2.25.0
next reply other threads:[~2020-01-23 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 20:00 Khem Raj [this message]
2020-01-23 20:00 ` [PATCH 1/4] perf: Pass LDSHARED and CCLD via EXTRA_OEMAKE Khem Raj
2020-01-23 20:00 ` [PATCH 2/4] ruby: Remove __has_include and __has_include_next from preprocessed header file Khem Raj
2020-01-23 20:00 ` [PATCH 3/4] nss: Pass NSS_USE_ARM_HW_CRYPTO as define in CFLAGS Khem Raj
2020-01-26 9:36 ` Martin Jansa
2020-01-23 20:00 ` [PATCH 4/4] libucontext: Add recipe 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=cover.1579809439.git.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 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.