From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: boost 1.69 -> 1.71 upgrade for 3.0?
Date: Thu, 22 Aug 2019 21:52:43 +0200 [thread overview]
Message-ID: <CANNYZj9nmZqD2C3zN7RVNQS3d8U0j0unO2fTpgzGmEwaBxgt1Q@mail.gmail.com> (raw)
In-Reply-To: <a01c66d2-4603-5633-9b3e-6180ba8c904d@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
On Thu, 22 Aug 2019 at 21:20, Randy MacLeod <randy.macleod@windriver.com>
wrote:
> I'm checking if you have done any work on upgrading the
> boost recipe? Trevor will work on it if you haven't started.
> He's relatively new to YP so depending on how easy the
> update is he might bail or need help or take a while.
>
I made a preliminary update to 1.70, but I had to hold it back because
there is a significant regression in do_install(). Bjam spins the CPU at
100% for many minutes, while making glacial progress with the installation.
I couldn't figure out what is it doing, and so decided to wait and see if
things get better with 1.71 (also all the major desktop distros are at
various older versions still, so the upstream is probably oblivious to the
problem).
The patch is here, so you can first check if you see the same problem, and
then if 1.71 helps:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=akanavin/package-version-updates-later&id=39bcdb4184a9108561249d5a89b69a9250ff686d
Alex
[-- Attachment #2: Type: text/html, Size: 1586 bytes --]
next prev parent reply other threads:[~2019-08-22 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 19:19 boost 1.69 -> 1.71 upgrade for 3.0? Randy MacLeod
2019-08-22 19:52 ` Alexander Kanavin [this message]
2019-08-26 9:21 ` Daniel Klauer
2019-08-26 14:17 ` Alexander Kanavin
2019-09-03 15:19 ` Ross Burton
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=CANNYZj9nmZqD2C3zN7RVNQS3d8U0j0unO2fTpgzGmEwaBxgt1Q@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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.