From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [morty][PATCH 1/2] ruby: update to 2.4.0
Date: Sun, 14 Jan 2018 13:05:10 +0000 [thread overview]
Message-ID: <1515935110.29722.214.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180112162002.9669-1-alexander.kanavin@linux.intel.com>
On Fri, 2018-01-12 at 18:20 +0200, Alexander Kanavin wrote:
> Existing version of ruby-native (2.2.5) was crashing on my machine
> (and others' too),
> yet a functional ruby is necessary to upgrade webkit to a version
> that less vulnerable
> to Spectre.
>
> I've performed the update by copying the ruby recipe directory over
> from the current
> pyro tree; if you want to see the list of specific commits, issue
> this command:
>
> git log 99656fecf4fa6e24ba49ecb7f26f893e733818a0 meta/recipes-
> devtools/ruby
> (up to commit e593d3aeb2ea5f08d6e0753133fe89e345b339e8)
Fails on musl:
https://autobuilder.yocto.io/builders/nightly-musl/builds/719/steps/BuildImages/logs/stdio
Not sure why ruby-native would fail on musl specifically so could be a
host issue (its on fedora26).
Cheers,
Richard
next prev parent reply other threads:[~2018-01-14 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:20 [morty][PATCH 1/2] ruby: update to 2.4.0 Alexander Kanavin
2018-01-12 16:20 ` [morty][PATCH 2/2] webkitgtk: update to 2.18.5 (includes Spectre mitigations; see commit description) Alexander Kanavin
2018-01-12 16:33 ` ✗ patchtest: failure for "[morty] ruby: update to 2.4.0..." and 1 more Patchwork
2018-01-14 13:05 ` Richard Purdie [this message]
2018-01-25 19:59 ` [morty][PATCH 1/2] ruby: update to 2.4.0 Khem Raj
2018-01-26 3:47 ` Andre McCurdy
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=1515935110.29722.214.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexander.kanavin@linux.intel.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