Hi,
On 04/07/2017 11:08 AM, Fathi Boudra wrote:
Hi Trevor,
On 6 April 2017 at 23:37, Trevor Woerner wrote:
On Thu, Apr 6, 2017 at 3:31 AM, Martin Jansa wrote:
In my world build it (surprisingly) didn't fail, good job Trevor!
Sadly, it does fail
Hi Trevor,
On 06/04/17 22:37, Trevor Woerner wrote:
> ...
> Currently I'm trying to figure out how to move past this version.
> After 53.0.2810.2 the current method OE uses to build chromium starts
> to fail because (as is my understanding) it was around this point that
> the chromium build
Hi Trevor,
On 6 April 2017 at 23:37, Trevor Woerner wrote:
> On Thu, Apr 6, 2017 at 3:31 AM, Martin Jansa wrote:
>> In my world build it (surprisingly) didn't fail, good job Trevor!
>
> Sadly, it does fail with one specific PACKAGECONFIG:
On Thu, Apr 6, 2017 at 3:31 AM, Martin Jansa wrote:
> In my world build it (surprisingly) didn't fail, good job Trevor!
Sadly, it does fail with one specific PACKAGECONFIG: ignore-lost-context
I have a fix which I've build-tested both for x11 and wayland with a
bunch of
In my world build it (surprisingly) didn't fail, good job Trevor!
Are you willing to check 2 QA issues which might be there in older version
as well?
chromium-54.0.2810.2: ELF binary
'/tmp/work/i586-oe-linux/chromium/54.0.2810.2-r0/packages-split/chromium/usr/bin/chromium/chrome'
has relocations
Tested by building for and running on:
- minnow
- raspi3 (32-bit)
- qemux86
- bbb
On-target testing includes:
- playing a video from youtube[1]
- running (and passing) the octane tests (js)[2]
Verified chromium-wayland still builds.
[1] http://youtube.com
[2] http://chromium.github.io/octane