From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [pyro][PATCH 0/3] Backports for pyro
Date: Thu, 7 Sep 2017 07:29:45 -0700 [thread overview]
Message-ID: <ecee6720-fdb0-dbd4-106f-bc235f32df9b@gmail.com> (raw)
In-Reply-To: <cover.1504713837.git.Martin.Jansa@gmail.com>
On 09/06/2017 09:09 AM, Martin Jansa wrote:
> All 3 are backports from master.
thanks,
all in pyro
- armin
>
> qemu and nspr change needed small tweak to apply for older version.
>
> qemu change is already backported to morty, which seems wrong that
> it's missing in pyro. (the morty patch also looks a bit differently than
> the version from master, see:
> "qemu: Backport a patch for recent glibc versions" commit in morty)
>
> The build with pyro still doesn't work on hosts with glibc-2.26.
>
> cross-localedef-native/2.25-r0 on host system with glibc-2.26
> is choking on it's own locale_t https://pastebin.com/udCzFA9L
> but more difficult to resolve here when it mixes host's headers
> from glibc-2.26 with glibc-2.25 code.
>
> I'll probably use LOCALE_GENERATION_WITH_CROSS-LOCALEDEF to bypass
> this, but it there is a plan to support Pyro on more recent hosts than
> this should be resolved as well
>
> The following changes since commit 1009498f23ad319825c00ba60a4693d15aada553:
>
> package.bbclass: Restore functionality to detect RPM dependencies (2017-08-30 23:59:53 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib jansa/pyro-backports
> http://cgit.openembedded.org/openembedded-core-contrib/log/?h=jansa/pyro-backports
>
> Khem Raj (3):
> icu: Fix build with glibc 2.26
> qemu: Replace use of struct ucontext with ucontext_t
> nspr: Fix build error due to missing stdint.h> include
>
> ...lace-struct-ucontext-with-ucontext_t-type.patch | 265 +++++++++++++++++++++
> meta/recipes-devtools/qemu/qemu_2.8.0.bb | 1 +
> .../icu/icu/0001-i18n-Drop-include-xlocale.h.patch | 31 +++
> meta/recipes-support/icu/icu_58.2.bb | 3 +-
> ...int.h-for-SSIZE_MAX-and-SIZE_MAX-definiti.patch | 30 +++
> meta/recipes-support/nspr/nspr_4.13.1.bb | 1 +
> 6 files changed, 330 insertions(+), 1 deletion(-)
> create mode 100644 meta/recipes-devtools/qemu/qemu/0001-replace-struct-ucontext-with-ucontext_t-type.patch
> create mode 100644 meta/recipes-support/icu/icu/0001-i18n-Drop-include-xlocale.h.patch
> create mode 100644 meta/recipes-support/nspr/nspr/0001-include-stdint.h-for-SSIZE_MAX-and-SIZE_MAX-definiti.patch
>
next prev parent reply other threads:[~2017-09-07 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 16:09 [pyro][PATCH 0/3] Backports for pyro Martin Jansa
2017-09-06 16:09 ` [pyro][PATCH 1/3] icu: Fix build with glibc 2.26 Martin Jansa
2017-09-06 16:09 ` [pyro][PATCH 2/3] qemu: Replace use of struct ucontext with ucontext_t Martin Jansa
2017-09-06 16:09 ` [pyro][PATCH 3/3] nspr: Fix build error due to missing stdint.h> include Martin Jansa
2017-09-07 14:29 ` akuster808 [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-25 14:07 [pyro][PATCH 0/3] Backports for pyro Martin Jansa
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=ecee6720-fdb0-dbd4-106f-bc235f32df9b@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@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