From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-14
Date: Thu, 16 May 2019 08:33:53 +0200 [thread overview]
Message-ID: <20190516083353.5cd7ae04@windsurf> (raw)
In-Reply-To: <20190515221703.GC32757@momiji>
Hello Adrian,
On Wed, 15 May 2019 22:17:03 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:
> > 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 ?\_(?)_/?
This build has BR2_ENABLE_DEBUG=y, and when BR2_ENABLE_DEBUG=y, the
CMake package infrastructure passes -DCMAKE_BUILD_TYPE=Debug. I assume
that's under this condition that assertions become enabled.
> 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.
Except that the build issue you're seeing is in master, and we're past
-rc1 (even -rc2 now), and therefore we generally don't take version
bumps in master, as we're too close to the release. Especially a
version bump on a complex package like wpewebkit, and for which the
version bump requires bumping the versions of a number of other
packages as well.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-16 6:33 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
2019-05-16 6:33 ` Thomas Petazzoni [this message]
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=20190516083353.5cd7ae04@windsurf \
--to=thomas.petazzoni@bootlin.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.