From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-14
Date: Wed, 15 May 2019 22:17:03 +0300 [thread overview]
Message-ID: <20190515221703.GC32757@momiji> (raw)
In-Reply-To: <20190515060039.F045C22920@silver.osuosl.org>
Hello,
On Wed, 15 May 2019 06:00:34 -0000, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> aarch64 | wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/39ccf985b3121342589167fe8bc0f88735318c28 |
> aarch64 | wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/fa8341c0b11c5ef30a4692927e90f64de5bf4e11 |
> aarch64 | wpebackend-fdo-1.0.1 | NOK | http://autobuild.buildroot.net/results/790c239fee8a59682927cb87ea9c1908a83d3c84 |
The wpebackend-fdo build failure would go away by applying Giulio's patch:
https://patchwork.ozlabs.org/patch/1085508/
> arm | wpewebkit-2.22.5 | NOK | http://autobuild.buildroot.net/results/645be27edc31037a9b1bb7ce0dc85440949b0846 |
This build failure of of the wpewebkit package is kind of odd: it looks like
with assertions enabled (as in: doing a debug build) uses some variables which
do not exist, and I wonder why we haven't seen this before?when working on
WebKit we routinely do debug builds ?\_(?)_/?
I think it is more worth it to push the update to WPE WebKit 2.24.x forward,
and this build failure would just go away.
Regards,
?Adri?n
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190515/22d82b26/attachment.asc>
next prev parent reply other threads:[~2019-05-15 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-14 Thomas Petazzoni
2019-05-15 19:17 ` Adrian Perez de Castro [this message]
2019-05-16 6:33 ` Thomas Petazzoni
2019-05-16 8:52 ` Adrian Perez de Castro
2019-05-16 9:06 ` Thomas Petazzoni
2019-05-26 11:35 ` Arnout Vandecappelle
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=20190515221703.GC32757@momiji \
--to=aperez@igalia.com \
--cc=buildroot@busybox.net \
/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.