[meta-browser] CFT: Chromium 62 in meta-browser

[meta-browser] CFT: Chromium 62 in meta-browser

[Raphael Kubo da Costa]

Hi everyone,

Like I said back in September, I'd like to merge the Chromium recipe
I've been maintaining independently [1] since last year into the
meta-browser layer so that more people can both benefit from it as well
as help maintain it. Currently, the meta-browser recipe is still
tracking Chromium 54 and ozone-wayland with Chromium 53, whereas my
recipe tracks the latest stable releases (it's currently at
62.0.3202.89).

[1] https://github.com/rakuco/meta-crosswalk

I don't want to just copy-paste my recipe into meta-browser in one giant
commit and call it a day though, so in parallel to maintaining my recipe
I've been working on "organically" turning the meta-browser recipe into
something that looks more similar to mine (while also landing a few bug
fixes into my recipe after looking at the meta-browser one). This way,
people can still track the commit history and know why each change was
done the way it was.

I believe this has finally reached a stage where it's ready for public
consumption, hence the CFT:

    https://github.com/rakuco/meta-browser/tree/chromium62

I'd like people to look at my commits and let me know if there's any big
issue that would prevent those changes from landing into meta-browser.
If everything's OK, I'd then start sending the patches to the list (or
pull requests on GitHub, whichever is preferred).

There are 60 new commits in my "chromium62" branch; the majority of them
are clean-ups, bug fixes and adjustments to the recipe. In fact, the
actual update from Chromium 54 to Chromium 62 only happens in the 58th
commit, and the biggest change is actually the move to GN (which I've
done separately and before the Chromium 62 update commit). Compared to
my meta-crosswalk Chromium recipe, the existing changes are mostly just
cosmetic (some variables are defined in different locations, the
available PACKAGECONFIG options are different etc), so it's been tested
on Yocto morty and rocko with GCC 5, 6 and 7.

Possibly controversial issues:
- The ozone-wayland recipe has been removed (this is actually commit
  #1). The ozone-wayland project Intel used to maintain has not been
  maintained in a very long time, and it is impossible to just get it to
  work with Chromium 62. I'd also rather not keep Chromium 53 around
  just because of it due to A) increased maintenance costs 2) we'd be
  shipping an ancient Chromium release with tons of security issues.

- musl support is currently broken. I've sent a few patches upstream
  lately and added a few musl-related changes to the Chromium 62 recipe,
  but getting the code to build requires a lot of time and
  determination, and if we don't have someone actively working with
  upstream it's just going to be an uphill battle that I am not willing
  to take upon myself.

- The 'ignore-lost-context' PACKAGECONFIG knob was removed. The patch
  it required no longer applies cleanly, its context refers a 5-year-old
  discussion and it is not clear if it is still necessary at all.

- It is no longer possible to run Chromium as root. Upstream has done
  some work on this front, and now really requires --no-sandbox to be
  passed on the command line for Chromium to run as root. I'd rather not
  swim against the current here.

- In the future, I'd like to revisit the other PACKAGECONFIG knobs as
  well. In particular, it is not clear to me if 'impl-side-painting' and
  'use-egl' are still needed at all, and I'd like to drop
  'component-build' to simplify the recipe and prevent anyone from using
  this option in production.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Otavio Salvador]

Hello Raphael,

On Thu, Nov 9, 2017 at 2:28 PM, Raphael Kubo da Costa
<raphael.kubo.da.costa@intel.com> wrote:
> Like I said back in September, I'd like to merge the Chromium recipe
> I've been maintaining independently [1] since last year into the
> meta-browser layer so that more people can both benefit from it as well
> as help maintain it. Currently, the meta-browser recipe is still
> tracking Chromium 54 and ozone-wayland with Chromium 53, whereas my
> recipe tracks the latest stable releases (it's currently at
> 62.0.3202.89).

First, I'd like to thank you for all this amazing work. Chromium is
indeed a giant project and its proper integration has some specific
challenges by itself...

...
> I'd like people to look at my commits and let me know if there's any big
> issue that would prevent those changes from landing into meta-browser.
> If everything's OK, I'd then start sending the patches to the list (or
> pull requests on GitHub, whichever is preferred).

I went through all the commits, one by one. There are few that might
need minor adjustments (as for example the removal of cups support
which should be moved to a PACKAGECONFIG) but in general, they are all
good. You did a great job making it very granular and well documented
:-)

I think this is huge enough that using a pull request so we can track
comments and progress makes sense. Do you mind creating one?

I think we will end picking individual commits on the beginning to
reduce the delta and keep going until we have the bump done. Do you
think it is a good way to handle this?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Raphael Kubo da Costa]

Hey Otavio, thanks for the quick response!

Otavio Salvador <otavio.salvador@ossystems.com.br> writes:
> Hello Raphael,
>
>> I'd like people to look at my commits and let me know if there's any big
>> issue that would prevent those changes from landing into meta-browser.
>> If everything's OK, I'd then start sending the patches to the list (or
>> pull requests on GitHub, whichever is preferred).
>
> I went through all the commits, one by one. There are few that might
> need minor adjustments (as for example the removal of cups support
> which should be moved to a PACKAGECONFIG) but in general, they are all
> good. You did a great job making it very granular and well documented
> :-)
>
> I think this is huge enough that using a pull request so we can track
> comments and progress makes sense. Do you mind creating one?
>
> I think we will end picking individual commits on the beginning to
> reduce the delta and keep going until we have the bump done. Do you
> think it is a good way to handle this?

I think that works, and it matches what I originally had in mind:
* Get people to look at the existing commits and raise any objections to
  any major "architectural" issues with the changes.
* Once everyone's on the same page, start sending patches in chunks
  (e.g. all dependency changes in one pull request).
* Once the clean-ups and bug fixes are in, send the big PRs (move to GN
  and update to M62).

I'll start splitting that branch into smaller ones for PRs, but I'll
also wait a little bit for others (such as Jacobo, Trevor and Khem) to
chime in as well.

The only bummer is that I'll be on holidays from 17th November to 8th
December so it may take a little longer than usual for me to get all the
changes landed.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Trevor Woerner]

Raphael,

On Thu, Nov 9, 2017 at 11:28 AM, Raphael Kubo da Costa
<raphael.kubo.da.costa@intel.com> wrote:
> There are 60 new commits in my "chromium62" branch

This work is utterly *brilliant*! BRAVO! Thanks so much for sticking with it.

> Possibly controversial issues:
> - The ozone-wayland recipe has been removed (this is actually commit
>   #1). The ozone-wayland project Intel used to maintain has not been
>   maintained in a very long time, and it is impossible to just get it to
>   work with Chromium 62. I'd also rather not keep Chromium 53 around
>   just because of it due to A) increased maintenance costs 2) we'd be
>   shipping an ancient Chromium release with tons of security issues.

No issues from me. Originally there was only one recipe that included
both wayland and x11 support together. I had proposed, then done the
work, to separate them out into two recipes because keeping them in
sync wasn't working. If nobody is keeping ozone-wayland working, it
doesn't work, and/or it's not being worked on upstream, then I have no
issues with it being removed. Just to be clear: if somebody finds it
useful and wants to support it, I'd be happy to see it come back. But
at this point it appears to be dead and I don't think it's worth
blacklisting.

> - musl support is currently broken. I've sent a few patches upstream
>   lately and added a few musl-related changes to the Chromium 62 recipe,
>   but getting the code to build requires a lot of time and
>   determination, and if we don't have someone actively working with
>   upstream it's just going to be an uphill battle that I am not willing
>   to take upon myself.

I'll have to defer to Khem on this one. As I've said before, I
strongly don't believe meta-browser (or any other layer other than
meta-musl) is the right place for musl support. Musl support should be
in meta-musl and not spread throughout the ecosystem for everyone else
to worry about. But I don't get the feeling that I "won" this
discussion in the past... ;-)

> - The 'ignore-lost-context' PACKAGECONFIG knob was removed. The patch
>   it required no longer applies cleanly, its context refers a 5-year-old
>   discussion and it is not clear if it is still necessary at all.

This seems fine to me. If anyone still wants to use the
--gpu-no-context-lost cmdline argument (or any other cmdline argument,
for that matter) without the patch, they can simply add it to the
chromium-wrapper.

> - In the future, I'd like to revisit the other PACKAGECONFIG knobs as
>   well. In particular, it is not clear to me if 'impl-side-painting' and
>   'use-egl' are still needed at all,

Sounds good.

> and I'd like to drop
>   'component-build' to simplify the recipe and prevent anyone from using
>   this option in production.

Yes! And if you wanted to remove DEBUG_BUILD too, I'd be okay with
that as well. I'm confused as to the status of DEBUG_BUILD, it seems
to be removed, but you're setting debug flags?

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ian Coolidge]

Hi All,

For what it's worth, I built this chromium62 for the nitrogen6x and I'm
getting Alignment traps when loading webpages.

Are there any obvious flags or compile options I'm missing here? I haven't
tied debugging into this yet, which is my next step here. Just wanted to
know if I was missing something obvious.

Thanks!
-Ian Coolidge

On Fri, Nov 10, 2017 at 11:49 AM, Trevor Woerner <twoerner@gmail.com> wrote:

> Raphael,
>
> On Thu, Nov 9, 2017 at 11:28 AM, Raphael Kubo da Costa
> <raphael.kubo.da.costa@intel.com> wrote:
> > There are 60 new commits in my "chromium62" branch
>
> This work is utterly *brilliant*! BRAVO! Thanks so much for sticking with
> it.
>
> > Possibly controversial issues:
> > - The ozone-wayland recipe has been removed (this is actually commit
> >   #1). The ozone-wayland project Intel used to maintain has not been
> >   maintained in a very long time, and it is impossible to just get it to
> >   work with Chromium 62. I'd also rather not keep Chromium 53 around
> >   just because of it due to A) increased maintenance costs 2) we'd be
> >   shipping an ancient Chromium release with tons of security issues.
>
> No issues from me. Originally there was only one recipe that included
> both wayland and x11 support together. I had proposed, then done the
> work, to separate them out into two recipes because keeping them in
> sync wasn't working. If nobody is keeping ozone-wayland working, it
> doesn't work, and/or it's not being worked on upstream, then I have no
> issues with it being removed. Just to be clear: if somebody finds it
> useful and wants to support it, I'd be happy to see it come back. But
> at this point it appears to be dead and I don't think it's worth
> blacklisting.
>
> > - musl support is currently broken. I've sent a few patches upstream
> >   lately and added a few musl-related changes to the Chromium 62 recipe,
> >   but getting the code to build requires a lot of time and
> >   determination, and if we don't have someone actively working with
> >   upstream it's just going to be an uphill battle that I am not willing
> >   to take upon myself.
>
> I'll have to defer to Khem on this one. As I've said before, I
> strongly don't believe meta-browser (or any other layer other than
> meta-musl) is the right place for musl support. Musl support should be
> in meta-musl and not spread throughout the ecosystem for everyone else
> to worry about. But I don't get the feeling that I "won" this
> discussion in the past... ;-)
>
> > - The 'ignore-lost-context' PACKAGECONFIG knob was removed. The patch
> >   it required no longer applies cleanly, its context refers a 5-year-old
> >   discussion and it is not clear if it is still necessary at all.
>
> This seems fine to me. If anyone still wants to use the
> --gpu-no-context-lost cmdline argument (or any other cmdline argument,
> for that matter) without the patch, they can simply add it to the
> chromium-wrapper.
>
> > - In the future, I'd like to revisit the other PACKAGECONFIG knobs as
> >   well. In particular, it is not clear to me if 'impl-side-painting' and
> >   'use-egl' are still needed at all,
>
> Sounds good.
>
> > and I'd like to drop
> >   'component-build' to simplify the recipe and prevent anyone from using
> >   this option in production.
>
> Yes! And if you wanted to remove DEBUG_BUILD too, I'd be okay with
> that as well. I'm confused as to the status of DEBUG_BUILD, it seems
> to be removed, but you're setting debug flags?
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Otavio Salvador]

On Fri, Nov 10, 2017 at 10:10 PM, Ian Coolidge <ian@boundarydevices.com> wrote:
...
> Are there any obvious flags or compile options I'm missing here? I haven't
> tied debugging into this yet, which is my next step here. Just wanted to
> know if I was missing something obvious.

Maybe this fixes it?

commit 568227133be3f9f015679df3525f6c4f86304fd0
Author: Khem Raj <raj.khem@gmail.com>
Date:   Tue Nov 7 15:26:52 2017 -0800

    gcc7/gcc6: Fix unaligned STRD issue on ARM

    Backport
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82445

    Fixes [YOCTO 12297]

    Signed-off-by: Khem Raj <raj.khem@gmail.com>
    Signed-off-by: Ross Burton <ross.burton@intel.com>

Please check if it helps you, otherwise please open a github issue so
we can keep track of it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ian Coolidge]

Where is this commit? I don't see 568227133be3f9f015679df3525f6c4f86304fd0
in meta-browser?

On Sat, Nov 11, 2017 at 9:25 AM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> On Fri, Nov 10, 2017 at 10:10 PM, Ian Coolidge <ian@boundarydevices.com>
> wrote:
> ...
> > Are there any obvious flags or compile options I'm missing here? I
> haven't
> > tied debugging into this yet, which is my next step here. Just wanted to
> > know if I was missing something obvious.
>
> Maybe this fixes it?
>
> commit 568227133be3f9f015679df3525f6c4f86304fd0
> Author: Khem Raj <raj.khem@gmail.com>
> Date:   Tue Nov 7 15:26:52 2017 -0800
>
>     gcc7/gcc6: Fix unaligned STRD issue on ARM
>
>     Backport
>     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82445
>
>     Fixes [YOCTO 12297]
>
>     Signed-off-by: Khem Raj <raj.khem@gmail.com>
>     Signed-off-by: Ross Burton <ross.burton@intel.com>
>
> Please check if it helps you, otherwise please open a github issue so
> we can keep track of it.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ian Coolidge]

Nevermind, found it. I'll test that.

On Mon, Nov 13, 2017 at 1:51 PM, Ian Coolidge <ian@boundarydevices.com>
wrote:

> Where is this commit? I don't see 568227133be3f9f015679df3525f6c4f86304fd0
> in meta-browser?
>
> On Sat, Nov 11, 2017 at 9:25 AM, Otavio Salvador <
> otavio.salvador@ossystems.com.br> wrote:
>
>> On Fri, Nov 10, 2017 at 10:10 PM, Ian Coolidge <ian@boundarydevices.com>
>> wrote:
>> ...
>> > Are there any obvious flags or compile options I'm missing here? I
>> haven't
>> > tied debugging into this yet, which is my next step here. Just wanted to
>> > know if I was missing something obvious.
>>
>> Maybe this fixes it?
>>
>> commit 568227133be3f9f015679df3525f6c4f86304fd0
>> Author: Khem Raj <raj.khem@gmail.com>
>> Date:   Tue Nov 7 15:26:52 2017 -0800
>>
>>     gcc7/gcc6: Fix unaligned STRD issue on ARM
>>
>>     Backport
>>     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82445
>>
>>     Fixes [YOCTO 12297]
>>
>>     Signed-off-by: Khem Raj <raj.khem@gmail.com>
>>     Signed-off-by: Ross Burton <ross.burton@intel.com>
>>
>> Please check if it helps you, otherwise please open a github issue so
>> we can keep track of it.
>>
>> --
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>
>
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Raphael Kubo da Costa]

Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> writes:
> I believe this has finally reached a stage where it's ready for public
> consumption, hence the CFT:
>
>     https://github.com/rakuco/meta-browser/tree/chromium62
>
> I'd like people to look at my commits and let me know if there's any big
> issue that would prevent those changes from landing into meta-browser.
> If everything's OK, I'd then start sending the patches to the list (or
> pull requests on GitHub, whichever is preferred).

Thanks to everyone who chimed in on GitHub and Otavio for merging my
pull requests.

We now have Chromium 62 in meta-browser, and I intend to keep the recipe
up-to-date from now on.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Martin Jansa]

Thanks for very good changes.

Yesterday I've tried to build this on "bitbake world" servers and the build
for qemuarm64 failed with:

| [30609/30609] python "../../build/toolchain/gcc_link_wrapper.py"
--output="./chrome" -- aarch64-oe-linux-g++  -fstack-protector-strong
-D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security
--sysroot=/home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot
-pie -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack
-Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread
-Wl,--as-needed -fuse-ld=gold -B -Wl,--icf=all -Wl,-O1 -Wl,--gc-sections
-Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,--export-dynamic -Wl,-O1
-Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong
-Wl,-z,relro,-z,now -o "./chrome" -Wl,--start-group @"./chrome.rsp"
-Wl,--end-group   -ldl -lpthread -lrt -lpangocairo-1.0 -lpango-1.0
-lgobject-2.0 -lglib-2.0 -lcairo -lX11 -lX11-xcb -lxcb -lXcomposite
-lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0
-lgthread-2.0 -lsmime3 -lnss3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 -lnspr4
-lxml2 -lexpat -lfontconfig -ldbus-1 -latomic -lXss -lfreetype -ljpeg
-lwebp -lwebpdemux -lwebpmux -lXrandr -lresolv -lgio-2.0 -lpci -lasound -lm
-lz -latk-1.0 -lFLAC -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
| FAILED: chrome
| python "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome" --
aarch64-oe-linux-g++  -fstack-protector-strong  -D_FORTIFY_SOURCE=2
-Wformat -Wformat-security -Werror=format-security
--sysroot=/home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot
-pie -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack
-Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread
-Wl,--as-needed -fuse-ld=gold -B -Wl,--icf=all -Wl,-O1 -Wl,--gc-sections
-Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,--export-dynamic -Wl,-O1
-Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong
-Wl,-z,relro,-z,now -o "./chrome" -Wl,--start-group @"./chrome.rsp"
-Wl,--end-group   -ldl -lpthread -lrt -lpangocairo-1.0 -lpango-1.0
-lgobject-2.0 -lglib-2.0 -lcairo -lX11 -lX11-xcb -lxcb -lXcomposite
-lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0
-lgthread-2.0 -lsmime3 -lnss3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 -lnspr4
-lxml2 -lexpat -lfontconfig -ldbus-1 -latomic -lXss -lfreetype -ljpeg
-lwebp -lwebpdemux -lwebpmux -lXrandr -lresolv -lgio-2.0 -lpci -lasound -lm
-lz -latk-1.0 -lFLAC -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
|
/home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot-native/usr/bin/aarch64-oe-linux/../../libexec/aarch64-oe-linux/gcc/aarch64-oe-linux/7.2.0/ld.gold:
out of memory
| collect2: error: ld returned 1 exit status
| ninja: build stopped: subcommand failed.

longer log in http://errors.yoctoproject.org/Errors/Details/158898/

I know what linking needs *a lot* of memory, but this server has 219GB
available and "only" 128GB from it can be taken by tmpfs, so there should
be still plenty RAM for successful linkage.

Build for x86_64 (on similar server) was successful.

Build for x86 + musl failed even before start, because there is missing
space in the append:
recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86 =
"yasm-native"
recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86-64 =
"yasm-native"

and unlike x86_64 it doesn't have trailing space in previous DEPENDS,
because of:
recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_libc-musl
= " libexecinfo"

Causing:
ERROR: Nothing PROVIDES 'libexecinfoyasm-native' (but
/home/jenkins/oe/world/shr-core/meta-browser/recipes-browser/chromium/
chromium_62.0.3202.89.bb DEPENDS on or otherwise requires it). Close
matches:
  libxinerama-native
  texinfo-native
  libyaml-native

I'll fix that missing space, but any other ideas why it might fail with out
of memory? Are you building for aarch64 as well?

Regards,



On Wed, Nov 15, 2017 at 1:04 PM, Raphael Kubo da Costa <
raphael.kubo.da.costa@intel.com> wrote:

> Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> writes:
> > I believe this has finally reached a stage where it's ready for public
> > consumption, hence the CFT:
> >
> >     https://github.com/rakuco/meta-browser/tree/chromium62
> >
> > I'd like people to look at my commits and let me know if there's any big
> > issue that would prevent those changes from landing into meta-browser.
> > If everything's OK, I'd then start sending the patches to the list (or
> > pull requests on GitHub, whichever is preferred).
>
> Thanks to everyone who chimed in on GitHub and Otavio for merging my
> pull requests.
>
> We now have Chromium 62 in meta-browser, and I intend to keep the recipe
> up-to-date from now on.
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Martin Jansa]

With the DEPENDS fix applied it still fails to build with musl:

http://errors.yoctoproject.org/Errors/Build/48408/
| In file included from ../../third_party/ffmpeg/libavutil/autorename_
libavutil_cpu.c:2:0:
| ../../third_party/ffmpeg/libavutil/cpu.c:42:10: fatal error:
sys/sysctl.h: No such file or directory
|  #include <sys/sysctl.h>
|           ^~~~~~~~~~~~~~
| compilation terminated.

I'm doing local qemuarm64 build now to see what happens before that out of
memory crash.


On Wed, Nov 15, 2017 at 1:38 PM, Martin Jansa <martin.jansa@gmail.com>
wrote:

> Thanks for very good changes.
>
> Yesterday I've tried to build this on "bitbake world" servers and the
> build for qemuarm64 failed with:
>
> | [30609/30609] python "../../build/toolchain/gcc_link_wrapper.py"
> --output="./chrome" -- aarch64-oe-linux-g++  -fstack-protector-strong
> -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security
> --sysroot=/home/jenkins/oe/world/shr-core/tmp-glibc/work/
> aarch64-oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot -pie
> -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack
> -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread
> -Wl,--as-needed -fuse-ld=gold -B -Wl,--icf=all -Wl,-O1 -Wl,--gc-sections
> -Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,--export-dynamic -Wl,-O1
> -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong
> -Wl,-z,relro,-z,now -o "./chrome" -Wl,--start-group @"./chrome.rsp"
> -Wl,--end-group   -ldl -lpthread -lrt -lpangocairo-1.0 -lpango-1.0
> -lgobject-2.0 -lglib-2.0 -lcairo -lX11 -lX11-xcb -lxcb -lXcomposite
> -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0
> -lgthread-2.0 -lsmime3 -lnss3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 -lnspr4
> -lxml2 -lexpat -lfontconfig -ldbus-1 -latomic -lXss -lfreetype -ljpeg
> -lwebp -lwebpdemux -lwebpmux -lXrandr -lresolv -lgio-2.0 -lpci -lasound -lm
> -lz -latk-1.0 -lFLAC -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
> | FAILED: chrome
> | python "../../build/toolchain/gcc_link_wrapper.py" --output="./chrome"
> -- aarch64-oe-linux-g++  -fstack-protector-strong  -D_FORTIFY_SOURCE=2
> -Wformat -Wformat-security -Werror=format-security
> --sysroot=/home/jenkins/oe/world/shr-core/tmp-glibc/work/
> aarch64-oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot -pie
> -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,noexecstack
> -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -Wl,--no-as-needed -lpthread
> -Wl,--as-needed -fuse-ld=gold -B -Wl,--icf=all -Wl,-O1 -Wl,--gc-sections
> -Wl,-rpath-link=. -Wl,--disable-new-dtags -Wl,--export-dynamic -Wl,-O1
> -Wl,--hash-style=gnu -Wl,--as-needed -fstack-protector-strong
> -Wl,-z,relro,-z,now -o "./chrome" -Wl,--start-group @"./chrome.rsp"
> -Wl,--end-group   -ldl -lpthread -lrt -lpangocairo-1.0 -lpango-1.0
> -lgobject-2.0 -lglib-2.0 -lcairo -lX11 -lX11-xcb -lxcb -lXcomposite
> -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lgmodule-2.0
> -lgthread-2.0 -lsmime3 -lnss3 -lsoftokn3 -lnssutil3 -lplds4 -lplc4 -lnspr4
> -lxml2 -lexpat -lfontconfig -ldbus-1 -latomic -lXss -lfreetype -ljpeg
> -lwebp -lwebpdemux -lwebpmux -lXrandr -lresolv -lgio-2.0 -lpci -lasound -lm
> -lz -latk-1.0 -lFLAC -lgtk-3 -lgdk-3 -lcairo-gobject -lgdk_pixbuf-2.0 -lxslt
> | /home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-
> oe-linux/chromium/62.0.3202.89-r0/recipe-sysroot-native/
> usr/bin/aarch64-oe-linux/../../libexec/aarch64-oe-linux/gcc/
> aarch64-oe-linux/7.2.0/ld.gold: out of memory
> | collect2: error: ld returned 1 exit status
> | ninja: build stopped: subcommand failed.
>
> longer log in http://errors.yoctoproject.org/Errors/Details/158898/
>
> I know what linking needs *a lot* of memory, but this server has 219GB
> available and "only" 128GB from it can be taken by tmpfs, so there should
> be still plenty RAM for successful linkage.
>
> Build for x86_64 (on similar server) was successful.
>
> Build for x86 + musl failed even before start, because there is missing
> space in the append:
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86 =
> "yasm-native"
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86-64 =
> "yasm-native"
>
> and unlike x86_64 it doesn't have trailing space in previous DEPENDS,
> because of:
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_libc-musl
> = " libexecinfo"
>
> Causing:
> ERROR: Nothing PROVIDES 'libexecinfoyasm-native' (but
> /home/jenkins/oe/world/shr-core/meta-browser/recipes-browser/chromium/
> chromium_62.0.3202.89.bb DEPENDS on or otherwise requires it). Close
> matches:
>   libxinerama-native
>   texinfo-native
>   libyaml-native
>
> I'll fix that missing space, but any other ideas why it might fail with
> out of memory? Are you building for aarch64 as well?
>
> Regards,
>
>
>
> On Wed, Nov 15, 2017 at 1:04 PM, Raphael Kubo da Costa <
> raphael.kubo.da.costa@intel.com> wrote:
>
>> Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> writes:
>> > I believe this has finally reached a stage where it's ready for public
>> > consumption, hence the CFT:
>> >
>> >     https://github.com/rakuco/meta-browser/tree/chromium62
>> >
>> > I'd like people to look at my commits and let me know if there's any big
>> > issue that would prevent those changes from landing into meta-browser.
>> > If everything's OK, I'd then start sending the patches to the list (or
>> > pull requests on GitHub, whichever is preferred).
>>
>> Thanks to everyone who chimed in on GitHub and Otavio for merging my
>> pull requests.
>>
>> We now have Chromium 62 in meta-browser, and I intend to keep the recipe
>> up-to-date from now on.
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Raphael Kubo da Costa]

Thanks for testing!

Martin Jansa <martin.jansa@gmail.com> writes:
> Thanks for very good changes.
>
> Yesterday I've tried to build this on "bitbake world" servers and the build
> for qemuarm64 failed with:
[...]
> longer log in http://errors.yoctoproject.org/Errors/Details/158898/
[...]
> I know what linking needs *a lot* of memory, but this server has 219GB
> available and "only" 128GB from it can be taken by tmpfs, so there should
> be still plenty RAM for successful linkage.

It had been a while since I'd last done an aarch64 build. I launched one
here and linking failed with relocation errors. I've pushed 4e5abf8
("chromium: Apply -g -> -g1 workaround for aarch64 as well"), which is
the same workaround I've been applying for other architectures, and
everything went fine.

> Build for x86_64 (on similar server) was successful.
>
> Build for x86 + musl failed even before start, because there is missing
> space in the append:
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86 =
> "yasm-native"
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86-64 =
> "yasm-native"
>
> and unlike x86_64 it doesn't have trailing space in previous DEPENDS,
> because of:
> recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_libc-musl
> = " libexecinfo"
>
> Causing:
> ERROR: Nothing PROVIDES 'libexecinfoyasm-native' (but
> /home/jenkins/oe/world/shr-core/meta-browser/recipes-browser/chromium/
> chromium_62.0.3202.89.bb DEPENDS on or otherwise requires it). Close
> matches:
>   libxinerama-native
>   texinfo-native
>   libyaml-native

Thanks for fixing the yasm bit.

As for musl: like I said in my original email and on GitHub, the musl
build is currently broken. Carrying tons of patches in the recipe is an
uphill battle, so unless someone takes the time to work with upstream I
don't think it makes much sense to try to keep the build working.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]

On Wed, Nov 15, 2017 at 06:08:49PM +0100, Raphael Kubo da Costa wrote:
> Thanks for testing!
> 
> Martin Jansa <martin.jansa@gmail.com> writes:
> > Thanks for very good changes.
> >
> > Yesterday I've tried to build this on "bitbake world" servers and the build
> > for qemuarm64 failed with:
> [...]
> > longer log in http://errors.yoctoproject.org/Errors/Details/158898/
> [...]
> > I know what linking needs *a lot* of memory, but this server has 219GB
> > available and "only" 128GB from it can be taken by tmpfs, so there should
> > be still plenty RAM for successful linkage.
> 
> It had been a while since I'd last done an aarch64 build. I launched one
> here and linking failed with relocation errors. I've pushed 4e5abf8
> ("chromium: Apply -g -> -g1 workaround for aarch64 as well"), which is
> the same workaround I've been applying for other architectures, and
> everything went fine.

With the latest version from you (62.0.3202.94) I also got relocation
errors instead of the out-of-memory one, see:

http://errors.yoctoproject.org/Errors/Build/48426/

I'm trying now with g1 as you suggested.

> 
> > Build for x86_64 (on similar server) was successful.
> >
> > Build for x86 + musl failed even before start, because there is missing
> > space in the append:
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86 =
> > "yasm-native"
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86-64 =
> > "yasm-native"
> >
> > and unlike x86_64 it doesn't have trailing space in previous DEPENDS,
> > because of:
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_libc-musl
> > = " libexecinfo"
> >
> > Causing:
> > ERROR: Nothing PROVIDES 'libexecinfoyasm-native' (but
> > /home/jenkins/oe/world/shr-core/meta-browser/recipes-browser/chromium/
> > chromium_62.0.3202.89.bb DEPENDS on or otherwise requires it). Close
> > matches:
> >   libxinerama-native
> >   texinfo-native
> >   libyaml-native
> 
> Thanks for fixing the yasm bit.
> 
> As for musl: like I said in my original email and on GitHub, the musl
> build is currently broken. Carrying tons of patches in the recipe is an
> uphill battle, so unless someone takes the time to work with upstream I
> don't think it makes much sense to try to keep the build working.

OK, fair enough, maybe Khem will again chime in and fix it for musl (in
the meantime we might blacklist it for musl that people don't wait for
the build to fail).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Kubo Da Costa, Raphael]

On Wed, 2017-11-15 at 18:41 +0100, Martin Jansa wrote:
> On Wed, Nov 15, 2017 at 06:08:49PM +0100, Raphael Kubo da Costa
> wrote:
> > Thanks for testing!
> > 
> > Martin Jansa <martin.jansa@gmail.com> writes:
> > > Thanks for very good changes.
> > > 
> > > Yesterday I've tried to build this on "bitbake world" servers and
> > > the build
> > > for qemuarm64 failed with:
> > 
> > [...]
> > > longer log in http://errors.yoctoproject.org/Errors/Details/15889
> > > 8/
> > 
> > [...]
> > > I know what linking needs *a lot* of memory, but this server has
> > > 219GB
> > > available and "only" 128GB from it can be taken by tmpfs, so
> > > there should
> > > be still plenty RAM for successful linkage.
> > 
> > It had been a while since I'd last done an aarch64 build. I
> > launched one
> > here and linking failed with relocation errors. I've pushed 4e5abf8
> > ("chromium: Apply -g -> -g1 workaround for aarch64 as well"), which
> > is
> > the same workaround I've been applying for other architectures, and
> > everything went fine.
> 
> With the latest version from you (62.0.3202.94) I also got relocation
> errors instead of the out-of-memory one, see:
> 
> http://errors.yoctoproject.org/Errors/Build/48426/
> 
> I'm trying now with g1 as you suggested.

.94 is still under review on GitHub, but it's what I tested
nonetheless. The relocation error shouldn't happen anymore, please make
sure that commit I mentioned is included in your tests.

> (in the meantime we might blacklist it for musl that people don't
> wait for the build to fail).

Sounds like a plan to me, just let me know if you'd like to do that
yourself, otherwise I'll get around to it tomorrow.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Khem Raj]

>> As for musl: like I said in my original email and on GitHub, the musl
>> build is currently broken. Carrying tons of patches in the recipe is an
>> uphill battle, so unless someone takes the time to work with upstream I
>> don't think it makes much sense to try to keep the build working.
>

musl is relatively newer and support for various components may not be upstream
but it is getting there. There is no alternative than to carry patches
as of now.
and keep forward porting them as the versions advance. We may never get all
of them upstreamed as is the case with many other large packages.

> OK, fair enough, maybe Khem will again chime in and fix it for musl (in
> the meantime we might blacklist it for musl that people don't wait for
> the build to fail).

The patches needs to be redone mostly. Its ok to blacklist it from now.
I wish someone besides me would have cared too.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ayoub Zaki]

Hello all,

I'm trying to build from the latest commit meta-browser:
a8bb1e779bc3565beacceadc4414816670f33475 with an imx6 using yocto pyro
branch with meta-freescale, however the build fails :

 [460/30779] touch obj/chrome/browser/search/local_ntp_code_generate.stamp
| [461/30779] touch obj/chrome/browser/search/generated.stamp
| [462/30779] python
../../mojo/public/tools/bindings/generate_type_mappings.py --output
gen/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings
| [463/30779] touch
obj/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings.stamp
| [464/30779] touch obj/chrome/browser/chrome_internal_resources_gen.stamp
| [465/30779] touch obj/chrome/browser/theme_properties.stamp
| [466/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
bookmarks --input ../../chrome/browser/resources/md_bookmarks --out_folder
gen/chrome/browser/resources/md_bookmarks --depfile
gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
| FAILED: gen/chrome/browser/resources/md_bookmarks/vulcanized.html
gen/chrome/browser/resources/md_bookmarks/crisper.js
| python ../../chrome/browser/resources/vulcanize_gn.py --host bookmarks
--input ../../chrome/browser/resources/md_bookmarks --out_folder
gen/chrome/browser/resources/md_bookmarks --depfile
gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
| ../../third_party/node/linux/node-linux-x64/bin/node
../../third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler
--exclude chrome://resources/html/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js
--exclude chrome://resources/css/roboto.css --exclude
chrome://resources/css/text_defaults.css --exclude
chrome://resources/css/text_defaults_md.css --exclude
chrome://resources/js/load_time_data.js --inline-css --inline-scripts
--rewrite-urls-in-templates --strip-comments --redirect
"chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
--redirect
"chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
--redirect "chrome://resources/css/|../../ui/webui/resources/css"
--redirect "chrome://resources/html/|../../ui/webui/resources/html"
--redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
"chrome://resources/polymer/v1_0/|../../third_party/polymer/v1_0/components-chromium"
--exclude strings.js --exclude chrome://bookmarks/strings.js --manifest-out
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/Release/gen/chrome/browser/resources/md_bookmarks/bookmarks_requestlist.txt
--root
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_bookmarks
--redirect
"chrome://bookmarks/|/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_bookmarks"
--out-dir gen/chrome/browser/resources/md_bookmarks/bundled --shell
bookmarks.html --in-html bookmarks.html failed:
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler.js:178
|         const [prefix, path] = redirect.split('|');
|               ^
|
| SyntaxError: Unexpected token [
|     at exports.runInThisContext (vm.js:53:16)
|     at Module._compile (module.js:373:25)
|     at Object.Module._extensions..js (module.js:416:10)
|     at Module.load (module.js:343:32)
|     at Function.Module._load (module.js:300:12)
|     at Function.Module.runMain (module.js:441:10)
|     at startup (node.js:140:18)
|     at node.js:1043:3
|
| Traceback (most recent call last):
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
<module>
|     main(sys.argv[1:])
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in main
|     manifest_out_path = _vulcanize(args.input, args)
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
_vulcanize
|     ] + in_html_args)
|   File "../../third_party/node/node.py", line 28, in RunNode
|     raise
| TypeError: exceptions must be old-style classes or derived from
BaseException, not NoneType
| [467/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
downloads --input ../../chrome/browser/resources/md_downloads --out_folder
gen/chrome/browser/resources/md_downloads --depfile
gen/chrome/browser/resources/md_downloads/build.d --html_in_files
downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
--insert_in_head \<base\ href=chrome://downloads\>
| FAILED: gen/chrome/browser/resources/md_downloads/vulcanized.html
gen/chrome/browser/resources/md_downloads/crisper.js
| python ../../chrome/browser/resources/vulcanize_gn.py --host downloads
--input ../../chrome/browser/resources/md_downloads --out_folder
gen/chrome/browser/resources/md_downloads --depfile
gen/chrome/browser/resources/md_downloads/build.d --html_in_files
downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
--insert_in_head \<base\ href=chrome://downloads\>
| ../../third_party/node/linux/node-linux-x64/bin/node
../../third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler
--exclude chrome://resources/html/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js
--exclude chrome://resources/css/roboto.css --exclude
chrome://resources/css/text_defaults.css --exclude
chrome://resources/css/text_defaults_md.css --exclude
chrome://resources/js/load_time_data.js --inline-css --inline-scripts
--rewrite-urls-in-templates --strip-comments --redirect
"chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
--redirect
"chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
--redirect "chrome://resources/css/|../../ui/webui/resources/css"
--redirect "chrome://resources/html/|../../ui/webui/resources/html"
--redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
"chrome://resources/polymer/v1_0/|../../third_party/polymer/v1_0/components-chromium"
--exclude strings.js --exclude chrome://downloads/strings.js --manifest-out
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/Release/gen/chrome/browser/resources/md_downloads/downloads_requestlist.txt
--root
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_downloads
--redirect
"chrome://downloads/|/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_downloads"
--out-dir gen/chrome/browser/resources/md_downloads/bundled --shell
downloads.html --in-html downloads.html failed:
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler.js:178
|         const [prefix, path] = redirect.split('|');
|               ^
|
| SyntaxError: Unexpected token [
|     at exports.runInThisContext (vm.js:53:16)
|     at Module._compile (module.js:373:25)
|     at Object.Module._extensions..js (module.js:416:10)
|     at Module.load (module.js:343:32)
|     at Function.Module._load (module.js:300:12)
|     at Function.Module.runMain (module.js:441:10)
|     at startup (node.js:140:18)
|     at node.js:1043:3
|
| Traceback (most recent call last):
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
<module>
|     main(sys.argv[1:])
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in main
|     manifest_out_path = _vulcanize(args.input, args)
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
_vulcanize
|     ] + in_html_args)
|   File "../../third_party/node/node.py", line 28, in RunNode
|     raise
| TypeError: exceptions must be old-style classes or derived from
BaseException, not NoneType
| [468/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
history --input ../../chrome/browser/resources/md_history --out_folder
gen/chrome/browser/resources/md_history --depfile
gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
lazy_load.html --html_out_files app.vulcanized.html
lazy_load.vulcanized.html --js_out_files app.crisper.js
lazy_load.crisper.js --exclude chrome://resources/html/util.html
chrome://history/constants.html
| FAILED: gen/chrome/browser/resources/md_history/app.vulcanized.html
gen/chrome/browser/resources/md_history/lazy_load.vulcanized.html
gen/chrome/browser/resources/md_history/app.crisper.js
gen/chrome/browser/resources/md_history/lazy_load.crisper.js
| python ../../chrome/browser/resources/vulcanize_gn.py --host history
--input ../../chrome/browser/resources/md_history --out_folder
gen/chrome/browser/resources/md_history --depfile
gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
lazy_load.html --html_out_files app.vulcanized.html
lazy_load.vulcanized.html --js_out_files app.crisper.js
lazy_load.crisper.js --exclude chrome://resources/html/util.html
chrome://history/constants.html
| ../../third_party/node/linux/node-linux-x64/bin/node
../../third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler
--exclude chrome://resources/html/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js
--exclude chrome://resources/css/roboto.css --exclude
chrome://resources/css/text_defaults.css --exclude
chrome://resources/css/text_defaults_md.css --exclude
chrome://resources/js/load_time_data.js --inline-css --inline-scripts
--rewrite-urls-in-templates --strip-comments --redirect
"chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
--redirect
"chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
--redirect "chrome://resources/css/|../../ui/webui/resources/css"
--redirect "chrome://resources/html/|../../ui/webui/resources/html"
--redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
"chrome://resources/polymer/v1_0/|../../third_party/polymer/v1_0/components-chromium"
--exclude chrome://resources/html/util.html --exclude
chrome://history/constants.html --exclude strings.js --exclude
chrome://history/strings.js --manifest-out
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/Release/gen/chrome/browser/resources/md_history/history_requestlist.txt
--root
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_history
--redirect
"chrome://history/|/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/chrome/browser/resources/md_history"
--out-dir gen/chrome/browser/resources/md_history/bundled --shell app.html
--in-html app.html --in-html lazy_load.html failed:
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler.js:178
|         const [prefix, path] = redirect.split('|');
|               ^
|
| SyntaxError: Unexpected token [
|     at exports.runInThisContext (vm.js:53:16)
|     at Module._compile (module.js:373:25)
|     at Object.Module._extensions..js (module.js:416:10)
|     at Module.load (module.js:343:32)
|     at Function.Module._load (module.js:300:12)
|     at Function.Module.runMain (module.js:441:10)
|     at startup (node.js:140:18)
|     at node.js:1043:3
|
| Traceback (most recent call last):
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
<module>
|     main(sys.argv[1:])
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in main
|     manifest_out_path = _vulcanize(args.input, args)
|   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
_vulcanize
|     ] + in_html_args)
|   File "../../third_party/node/node.py", line 28, in RunNode
|     raise
| TypeError: exceptions must be old-style classes or derived from
BaseException, not NoneType
| [469/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
-mfloat-abi=hard
--sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
-MMD -MF obj/base/base/shared_memory_tracker.o.d -DUSE_SYMBOLIZE
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
-DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/glib-2.0/include
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-missing-field-initializers -Wno-unused-parameter -fomit-frame-pointer
-g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
-std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
-fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src/debug/chromium/62.0.3202.94-r0
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot-native=
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
-g1 -c ../../base/memory/shared_memory_tracker.cc -o
obj/base/base/shared_memory_tracker.o
| [470/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
-mfloat-abi=hard
--sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
-MMD -MF obj/chrome/common/ini_parser/ini_parser.o.d
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
-DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/glib-2.0/include
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
-fdata-sections -ffunction-sections -fomit-frame-pointer -g0
-fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
-fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src/debug/chromium/62.0.3202.94-r0
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot-native=
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
-g1 -c ../../chrome/common/ini_parser.cc -o
obj/chrome/common/ini_parser/ini_parser.o
| [471/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
-mfloat-abi=hard
--sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
-MMD -MF
obj/chrome/app/shutdown_signal_handlers/shutdown_signal_handlers_posix.o.d
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
-DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/glib-2.0/include
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
-fdata-sections -ffunction-sections -fomit-frame-pointer -g0
-fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
-fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src/debug/chromium/62.0.3202.94-r0
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot-native=
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
-g1 -c ../../chrome/app/shutdown_signal_handlers_posix.cc -o
obj/chrome/app/shutdown_signal_handlers/shutdown_signal_handlers_posix.o
| [472/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
-mfloat-abi=hard
--sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
-MMD -MF obj/base/base/activity_analyzer.o.d -DUSE_SYMBOLIZE
-DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
-DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
-I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/glib-2.0/include
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-missing-field-initializers -Wno-unused-parameter -fomit-frame-pointer
-g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
-std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
-fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src/debug/chromium/62.0.3202.94-r0
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot-native=
-fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
-g1 -c ../../base/debug/activity_analyzer.cc -o
obj/base/base/activity_analyzer.o
| [473/30779] python
../../tools/metrics/histograms/generate_expired_histograms_array.py
-nchrome_metrics -ogen -Hchrome/browser/metrics/expired_histograms_array.h
../../tools/metrics/histograms/histograms.xml
../../tools/metrics/histograms/enums.xml
| ninja: build stopped: subcommand failed.
| WARNING:
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/temp/run.do_compile.13059:1
exit 1 from 'ninja -v -j 8 chrome chrome_sandbox chromedriver'
| ERROR: Function failed: do_compile (log file is located at
/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/temp/log.do_compile.13059)
ERROR: Task
(/opt/yocto/pyro/meta-browser/recipes-browser/chromium/chromium_62.0.3202.94.bb:do_compile)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 3903 tasks of which 3721 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/opt/yocto/pyro/meta-browser/recipes-browser/chromium/chromium_62.0.3202.94.bb:
do_compile
Summary: There were 12 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Which tag/commit is know to build correctly ?

Thank you !

Best regards

On Wed, Nov 15, 2017 at 8:34 PM, Khem Raj <raj.khem@gmail.com> wrote:

> >> As for musl: like I said in my original email and on GitHub, the musl
> >> build is currently broken. Carrying tons of patches in the recipe is an
> >> uphill battle, so unless someone takes the time to work with upstream I
> >> don't think it makes much sense to try to keep the build working.
> >
>
> musl is relatively newer and support for various components may not be
> upstream
> but it is getting there. There is no alternative than to carry patches
> as of now.
> and keep forward porting them as the versions advance. We may never get all
> of them upstreamed as is the case with many other large packages.
>
> > OK, fair enough, maybe Khem will again chime in and fix it for musl (in
> > the meantime we might blacklist it for musl that people don't wait for
> > the build to fail).
>
> The patches needs to be redone mostly. Its ok to blacklist it from now.
> I wish someone besides me would have cared too.
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ian Coolidge]

I'm not sure this build has been tested on Pyro. I'd use Rocko or master
when building this chromium.

I've built this on Rocko on the imx6 just fine. Granted it doesn't work
properly right now for me, but it built fine.

On Thu, Nov 23, 2017 at 2:22 AM, Ayoub Zaki <ayoub.zaki@googlemail.com>
wrote:

> Hello all,
>
> I'm trying to build from the latest commit meta-browser:
> a8bb1e779bc3565beacceadc4414816670f33475 with an imx6 using yocto pyro
> branch with meta-freescale, however the build fails :
>
>  [460/30779] touch obj/chrome/browser/search/local_ntp_code_generate.stamp
> | [461/30779] touch obj/chrome/browser/search/generated.stamp
> | [462/30779] python
> ../../mojo/public/tools/bindings/generate_type_mappings.py --output
> gen/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings
> | [463/30779] touch
> obj/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings.stamp
> | [464/30779] touch obj/chrome/browser/chrome_internal_resources_gen.stamp
> | [465/30779] touch obj/chrome/browser/theme_properties.stamp
> | [466/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
> bookmarks --input ../../chrome/browser/resources/md_bookmarks --out_folder
> gen/chrome/browser/resources/md_bookmarks --depfile
> gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
> bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
> | FAILED: gen/chrome/browser/resources/md_bookmarks/vulcanized.html
> gen/chrome/browser/resources/md_bookmarks/crisper.js
> | python ../../chrome/browser/resources/vulcanize_gn.py --host bookmarks
> --input ../../chrome/browser/resources/md_bookmarks --out_folder
> gen/chrome/browser/resources/md_bookmarks --depfile
> gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
> bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
> | ../../third_party/node/linux/node-linux-x64/bin/node
> ../../third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler
> --exclude chrome://resources/html/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
> chrome://resources/polymer/v1_0/web-animations-js/web-
> animations-next-lite.min.js
> --exclude chrome://resources/css/roboto.css --exclude
> chrome://resources/css/text_defaults.css --exclude
> chrome://resources/css/text_defaults_md.css --exclude
> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
> --rewrite-urls-in-templates --strip-comments --redirect
> "chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
> --redirect
> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
> --redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
> "chrome://resources/polymer/v1_0/|../../third_party/
> polymer/v1_0/components-chromium"
> --exclude strings.js --exclude chrome://bookmarks/strings.js --manifest-out
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/out/Release/gen/chrome/browser/resources/md_bookmarks/bookmarks_
> requestlist.txt
> --root
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/chrome/browser/resources/md_bookmarks
> --redirect
> "chrome://bookmarks/|/opt/yocto/pyro/build/tmp/work/
> armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-
> r0/chromium-62.0.3202.94/chrome/browser/resources/md_bookmarks"
> --out-dir gen/chrome/browser/resources/md_bookmarks/bundled --shell
> bookmarks.html --in-html bookmarks.html failed:
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler.js:178
> |         const [prefix, path] = redirect.split('|');
> |               ^
> |
> | SyntaxError: Unexpected token [
> |     at exports.runInThisContext (vm.js:53:16)
> |     at Module._compile (module.js:373:25)
> |     at Object.Module._extensions..js (module.js:416:10)
> |     at Module.load (module.js:343:32)
> |     at Function.Module._load (module.js:300:12)
> |     at Function.Module.runMain (module.js:441:10)
> |     at startup (node.js:140:18)
> |     at node.js:1043:3
> |
> | Traceback (most recent call last):
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
> <module>
> |     main(sys.argv[1:])
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
> main
> |     manifest_out_path = _vulcanize(args.input, args)
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
> _vulcanize
> |     ] + in_html_args)
> |   File "../../third_party/node/node.py", line 28, in RunNode
> |     raise
> | TypeError: exceptions must be old-style classes or derived from
> BaseException, not NoneType
> | [467/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
> downloads --input ../../chrome/browser/resources/md_downloads --out_folder
> gen/chrome/browser/resources/md_downloads --depfile
> gen/chrome/browser/resources/md_downloads/build.d --html_in_files
> downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
> --insert_in_head \<base\ href=chrome://downloads\>
> | FAILED: gen/chrome/browser/resources/md_downloads/vulcanized.html
> gen/chrome/browser/resources/md_downloads/crisper.js
> | python ../../chrome/browser/resources/vulcanize_gn.py --host downloads
> --input ../../chrome/browser/resources/md_downloads --out_folder
> gen/chrome/browser/resources/md_downloads --depfile
> gen/chrome/browser/resources/md_downloads/build.d --html_in_files
> downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
> --insert_in_head \<base\ href=chrome://downloads\>
> | ../../third_party/node/linux/node-linux-x64/bin/node
> ../../third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler
> --exclude chrome://resources/html/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
> chrome://resources/polymer/v1_0/web-animations-js/web-
> animations-next-lite.min.js
> --exclude chrome://resources/css/roboto.css --exclude
> chrome://resources/css/text_defaults.css --exclude
> chrome://resources/css/text_defaults_md.css --exclude
> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
> --rewrite-urls-in-templates --strip-comments --redirect
> "chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
> --redirect
> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
> --redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
> "chrome://resources/polymer/v1_0/|../../third_party/
> polymer/v1_0/components-chromium"
> --exclude strings.js --exclude chrome://downloads/strings.js --manifest-out
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/out/Release/gen/chrome/browser/resources/md_downloads/downloads_
> requestlist.txt
> --root
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/chrome/browser/resources/md_downloads
> --redirect
> "chrome://downloads/|/opt/yocto/pyro/build/tmp/work/
> armv7ahf-neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-
> r0/chromium-62.0.3202.94/chrome/browser/resources/md_downloads"
> --out-dir gen/chrome/browser/resources/md_downloads/bundled --shell
> downloads.html --in-html downloads.html failed:
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler.js:178
> |         const [prefix, path] = redirect.split('|');
> |               ^
> |
> | SyntaxError: Unexpected token [
> |     at exports.runInThisContext (vm.js:53:16)
> |     at Module._compile (module.js:373:25)
> |     at Object.Module._extensions..js (module.js:416:10)
> |     at Module.load (module.js:343:32)
> |     at Function.Module._load (module.js:300:12)
> |     at Function.Module.runMain (module.js:441:10)
> |     at startup (node.js:140:18)
> |     at node.js:1043:3
> |
> | Traceback (most recent call last):
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
> <module>
> |     main(sys.argv[1:])
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
> main
> |     manifest_out_path = _vulcanize(args.input, args)
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
> _vulcanize
> |     ] + in_html_args)
> |   File "../../third_party/node/node.py", line 28, in RunNode
> |     raise
> | TypeError: exceptions must be old-style classes or derived from
> BaseException, not NoneType
> | [468/30779] python ../../chrome/browser/resources/vulcanize_gn.py --host
> history --input ../../chrome/browser/resources/md_history --out_folder
> gen/chrome/browser/resources/md_history --depfile
> gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
> lazy_load.html --html_out_files app.vulcanized.html
> lazy_load.vulcanized.html --js_out_files app.crisper.js
> lazy_load.crisper.js --exclude chrome://resources/html/util.html
> chrome://history/constants.html
> | FAILED: gen/chrome/browser/resources/md_history/app.vulcanized.html
> gen/chrome/browser/resources/md_history/lazy_load.vulcanized.html
> gen/chrome/browser/resources/md_history/app.crisper.js
> gen/chrome/browser/resources/md_history/lazy_load.crisper.js
> | python ../../chrome/browser/resources/vulcanize_gn.py --host history
> --input ../../chrome/browser/resources/md_history --out_folder
> gen/chrome/browser/resources/md_history --depfile
> gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
> lazy_load.html --html_out_files app.vulcanized.html
> lazy_load.vulcanized.html --js_out_files app.crisper.js
> lazy_load.crisper.js --exclude chrome://resources/html/util.html
> chrome://history/constants.html
> | ../../third_party/node/linux/node-linux-x64/bin/node
> ../../third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler
> --exclude chrome://resources/html/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
> chrome://resources/polymer/v1_0/web-animations-js/web-
> animations-next-lite.min.js
> --exclude chrome://resources/css/roboto.css --exclude
> chrome://resources/css/text_defaults.css --exclude
> chrome://resources/css/text_defaults_md.css --exclude
> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
> --rewrite-urls-in-templates --strip-comments --redirect
> "chrome://resources/cr_components/|../../ui/webui/resources/cr_components"
> --redirect
> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
> --redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect
> "chrome://resources/polymer/v1_0/|../../third_party/
> polymer/v1_0/components-chromium"
> --exclude chrome://resources/html/util.html --exclude
> chrome://history/constants.html --exclude strings.js --exclude
> chrome://history/strings.js --manifest-out
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/out/Release/gen/chrome/browser/resources/md_history/
> history_requestlist.txt
> --root
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/chrome/browser/resources/md_history
> --redirect
> "chrome://history/|/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
> chromium-62.0.3202.94/chrome/browser/resources/md_history"
> --out-dir gen/chrome/browser/resources/md_history/bundled --shell app.html
> --in-html app.html --in-html lazy_load.html failed:
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.
> 94/third_party/node/node_modules/polymer-bundler/lib/
> bin/polymer-bundler.js:178
> |         const [prefix, path] = redirect.split('|');
> |               ^
> |
> | SyntaxError: Unexpected token [
> |     at exports.runInThisContext (vm.js:53:16)
> |     at Module._compile (module.js:373:25)
> |     at Object.Module._extensions..js (module.js:416:10)
> |     at Module.load (module.js:343:32)
> |     at Function.Module._load (module.js:300:12)
> |     at Function.Module.runMain (module.js:441:10)
> |     at startup (node.js:140:18)
> |     at node.js:1043:3
> |
> | Traceback (most recent call last):
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
> <module>
> |     main(sys.argv[1:])
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
> main
> |     manifest_out_path = _vulcanize(args.input, args)
> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
> _vulcanize
> |     ] + in_html_args)
> |   File "../../third_party/node/node.py", line 28, in RunNode
> |     raise
> | TypeError: exceptions must be old-style classes or derived from
> BaseException, not NoneType
> | [469/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
> -mfloat-abi=hard
> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-
> imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
> -MMD -MF obj/base/base/shared_memory_tracker.o.d -DUSE_SYMBOLIZE
> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/
> lib/glib-2.0/include
> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
> -Wno-missing-field-initializers -Wno-unused-parameter -fomit-frame-pointer
> -g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
> -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/
> src/debug/chromium/62.0.3202.94-r0
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
> recipe-sysroot-native=
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
> -g1 -c ../../base/memory/shared_memory_tracker.cc -o
> obj/base/base/shared_memory_tracker.o
> | [470/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
> -mfloat-abi=hard
> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-
> imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
> -MMD -MF obj/chrome/common/ini_parser/ini_parser.o.d
> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
> -DDYNAMIC_ANNOTATIONS_ENABLED=0
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/
> lib/glib-2.0/include
> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
> -fdata-sections -ffunction-sections -fomit-frame-pointer -g0
> -fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/
> src/debug/chromium/62.0.3202.94-r0
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
> recipe-sysroot-native=
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
> -g1 -c ../../chrome/common/ini_parser.cc -o
> obj/chrome/common/ini_parser/ini_parser.o
> | [471/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
> -mfloat-abi=hard
> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-
> imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
> -MMD -MF
> obj/chrome/app/shutdown_signal_handlers/shutdown_signal_handlers_posix.o.d
> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
> -DDYNAMIC_ANNOTATIONS_ENABLED=0
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/
> lib/glib-2.0/include
> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
> -fdata-sections -ffunction-sections -fomit-frame-pointer -g0
> -fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/
> src/debug/chromium/62.0.3202.94-r0
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
> recipe-sysroot-native=
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
> -g1 -c ../../chrome/app/shutdown_signal_handlers_posix.cc -o
> obj/chrome/app/shutdown_signal_handlers/shutdown_signal_handlers_posix.o
> | [472/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
> -mfloat-abi=hard
> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-
> imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
> -MMD -MF obj/base/base/activity_analyzer.o.d -DUSE_SYMBOLIZE
> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/
> lib/glib-2.0/include
> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
> -Wno-missing-field-initializers -Wno-unused-parameter -fomit-frame-pointer
> -g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
> -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/
> src/debug/chromium/62.0.3202.94-r0
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
> recipe-sysroot-native=
> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-
> neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
> -g1 -c ../../base/debug/activity_analyzer.cc -o
> obj/base/base/activity_analyzer.o
> | [473/30779] python
> ../../tools/metrics/histograms/generate_expired_histograms_array.py
> -nchrome_metrics -ogen -Hchrome/browser/metrics/expired_histograms_array.h
> ../../tools/metrics/histograms/histograms.xml
> ../../tools/metrics/histograms/enums.xml
> | ninja: build stopped: subcommand failed.
> | WARNING:
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/temp/run.do_compile.13059:1
> exit 1 from 'ninja -v -j 8 chrome chrome_sandbox chromedriver'
> | ERROR: Function failed: do_compile (log file is located at
> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-
> linux-gnueabi/chromium/62.0.3202.94-r0/temp/log.do_compile.13059)
> ERROR: Task
> (/opt/yocto/pyro/meta-browser/recipes-browser/chromium/
> chromium_62.0.3202.94.bb:do_compile)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 3903 tasks of which 3721 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>
> /opt/yocto/pyro/meta-browser/recipes-browser/chromium/chrom
> ium_62.0.3202.94.bb:
> do_compile
> Summary: There were 12 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
> Which tag/commit is know to build correctly ?
>
> Thank you !
>
> Best regards
>
> On Wed, Nov 15, 2017 at 8:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
> > >> As for musl: like I said in my original email and on GitHub, the musl
> > >> build is currently broken. Carrying tons of patches in the recipe is
> an
> > >> uphill battle, so unless someone takes the time to work with upstream
> I
> > >> don't think it makes much sense to try to keep the build working.
> > >
> >
> > musl is relatively newer and support for various components may not be
> > upstream
> > but it is getting there. There is no alternative than to carry patches
> > as of now.
> > and keep forward porting them as the versions advance. We may never get
> all
> > of them upstreamed as is the case with many other large packages.
> >
> > > OK, fair enough, maybe Khem will again chime in and fix it for musl (in
> > > the meantime we might blacklist it for musl that people don't wait for
> > > the build to fail).
> >
> > The patches needs to be redone mostly. Its ok to blacklist it from now.
> > I wish someone besides me would have cared too.
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ayoub Zaki]

Hi Ian,

Thank you, indeed I used rocko branches and it seems to build and also run
on an iMX6!
I use a mainline kernel 4.14  and with iMX6 Etnaviv GPU acceleration
support.
It's not clear for me how to enable GPU acceleration with chromium +
Etnaviv :
I tried the switch --use-gl=any,  it starts up but when running WebGL demo
Chromium/Etnaviv is crashing...
For normal browsing it works just fine however I noticed that CPU
consumption is very high > 50%
Anyone having better experience with Chromium + HW accleration support on
iMX6 ?

Best regards,

On Tue, Nov 28, 2017 at 1:52 AM, Ian Coolidge <ian@boundarydevices.com>
wrote:

> I'm not sure this build has been tested on Pyro. I'd use Rocko or master
> when building this chromium.
>
> I've built this on Rocko on the imx6 just fine. Granted it doesn't work
> properly right now for me, but it built fine.
>
> On Thu, Nov 23, 2017 at 2:22 AM, Ayoub Zaki <ayoub.zaki@googlemail.com>
> wrote:
>
>> Hello all,
>>
>> I'm trying to build from the latest commit meta-browser:
>> a8bb1e779bc3565beacceadc4414816670f33475 with an imx6 using yocto pyro
>> branch with meta-freescale, however the build fails :
>>
>>  [460/30779] touch obj/chrome/browser/search/loca
>> l_ntp_code_generate.stamp
>> | [461/30779] touch obj/chrome/browser/search/generated.stamp
>> | [462/30779] python
>> ../../mojo/public/tools/bindings/generate_type_mappings.py --output
>> gen/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings
>> | [463/30779] touch
>> obj/chrome/browser/ui/webui/omnibox/mojo_bindings__type_mappings.stamp
>> | [464/30779] touch obj/chrome/browser/chrome_inte
>> rnal_resources_gen.stamp
>> | [465/30779] touch obj/chrome/browser/theme_properties.stamp
>> | [466/30779] python ../../chrome/browser/resources/vulcanize_gn.py
>> --host
>> bookmarks --input ../../chrome/browser/resources/md_bookmarks
>> --out_folder
>> gen/chrome/browser/resources/md_bookmarks --depfile
>> gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
>> bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
>> | FAILED: gen/chrome/browser/resources/md_bookmarks/vulcanized.html
>> gen/chrome/browser/resources/md_bookmarks/crisper.js
>> | python ../../chrome/browser/resources/vulcanize_gn.py --host bookmarks
>> --input ../../chrome/browser/resources/md_bookmarks --out_folder
>> gen/chrome/browser/resources/md_bookmarks --depfile
>> gen/chrome/browser/resources/md_bookmarks/build.d --html_in_files
>> bookmarks.html --html_out_files vulcanized.html --js_out_files crisper.js
>> | ../../third_party/node/linux/node-linux-x64/bin/node
>> ../../third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler
>> --exclude chrome://resources/html/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
>> chrome://resources/polymer/v1_0/web-animations-js/web-animat
>> ions-next-lite.min.js
>> --exclude chrome://resources/css/roboto.css --exclude
>> chrome://resources/css/text_defaults.css --exclude
>> chrome://resources/css/text_defaults_md.css --exclude
>> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
>> --rewrite-urls-in-templates --strip-comments --redirect
>> "chrome://resources/cr_components/|../../ui/webui/resources/
>> cr_components"
>> --redirect
>> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
>> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
>> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
>> --redirect "chrome://resources/js/|../../ui/webui/resources/js"
>> --redirect
>> "chrome://resources/polymer/v1_0/|../../third_party/polymer/
>> v1_0/components-chromium"
>> --exclude strings.js --exclude chrome://bookmarks/strings.js
>> --manifest-out
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/
>> Release/gen/chrome/browser/resources/md_bookmarks/
>> bookmarks_requestlist.txt
>> --root
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> chrome/browser/resources/md_bookmarks
>> --redirect
>> "chrome://bookmarks/|/opt/yocto/pyro/build/tmp/work/armv7ahf
>> -neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
>> chromium-62.0.3202.94/chrome/browser/resources/md_bookmarks"
>> --out-dir gen/chrome/browser/resources/md_bookmarks/bundled --shell
>> bookmarks.html --in-html bookmarks.html failed:
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler.js:178
>> |         const [prefix, path] = redirect.split('|');
>> |               ^
>> |
>> | SyntaxError: Unexpected token [
>> |     at exports.runInThisContext (vm.js:53:16)
>> |     at Module._compile (module.js:373:25)
>> |     at Object.Module._extensions..js (module.js:416:10)
>> |     at Module.load (module.js:343:32)
>> |     at Function.Module._load (module.js:300:12)
>> |     at Function.Module.runMain (module.js:441:10)
>> |     at startup (node.js:140:18)
>> |     at node.js:1043:3
>> |
>> | Traceback (most recent call last):
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
>> <module>
>> |     main(sys.argv[1:])
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
>> main
>> |     manifest_out_path = _vulcanize(args.input, args)
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
>> _vulcanize
>> |     ] + in_html_args)
>> |   File "../../third_party/node/node.py", line 28, in RunNode
>> |     raise
>> | TypeError: exceptions must be old-style classes or derived from
>> BaseException, not NoneType
>> | [467/30779] python ../../chrome/browser/resources/vulcanize_gn.py
>> --host
>> downloads --input ../../chrome/browser/resources/md_downloads
>> --out_folder
>> gen/chrome/browser/resources/md_downloads --depfile
>> gen/chrome/browser/resources/md_downloads/build.d --html_in_files
>> downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
>> --insert_in_head \<base\ href=chrome://downloads\>
>> | FAILED: gen/chrome/browser/resources/md_downloads/vulcanized.html
>> gen/chrome/browser/resources/md_downloads/crisper.js
>> | python ../../chrome/browser/resources/vulcanize_gn.py --host downloads
>> --input ../../chrome/browser/resources/md_downloads --out_folder
>> gen/chrome/browser/resources/md_downloads --depfile
>> gen/chrome/browser/resources/md_downloads/build.d --html_in_files
>> downloads.html --html_out_files vulcanized.html --js_out_files crisper.js
>> --insert_in_head \<base\ href=chrome://downloads\>
>> | ../../third_party/node/linux/node-linux-x64/bin/node
>> ../../third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler
>> --exclude chrome://resources/html/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
>> chrome://resources/polymer/v1_0/web-animations-js/web-animat
>> ions-next-lite.min.js
>> --exclude chrome://resources/css/roboto.css --exclude
>> chrome://resources/css/text_defaults.css --exclude
>> chrome://resources/css/text_defaults_md.css --exclude
>> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
>> --rewrite-urls-in-templates --strip-comments --redirect
>> "chrome://resources/cr_components/|../../ui/webui/resources/
>> cr_components"
>> --redirect
>> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
>> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
>> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
>> --redirect "chrome://resources/js/|../../ui/webui/resources/js"
>> --redirect
>> "chrome://resources/polymer/v1_0/|../../third_party/polymer/
>> v1_0/components-chromium"
>> --exclude strings.js --exclude chrome://downloads/strings.js
>> --manifest-out
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/
>> Release/gen/chrome/browser/resources/md_downloads/
>> downloads_requestlist.txt
>> --root
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> chrome/browser/resources/md_downloads
>> --redirect
>> "chrome://downloads/|/opt/yocto/pyro/build/tmp/work/armv7ahf
>> -neon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/
>> chromium-62.0.3202.94/chrome/browser/resources/md_downloads"
>> --out-dir gen/chrome/browser/resources/md_downloads/bundled --shell
>> downloads.html --in-html downloads.html failed:
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler.js:178
>> |         const [prefix, path] = redirect.split('|');
>> |               ^
>> |
>> | SyntaxError: Unexpected token [
>> |     at exports.runInThisContext (vm.js:53:16)
>> |     at Module._compile (module.js:373:25)
>> |     at Object.Module._extensions..js (module.js:416:10)
>> |     at Module.load (module.js:343:32)
>> |     at Function.Module._load (module.js:300:12)
>> |     at Function.Module.runMain (module.js:441:10)
>> |     at startup (node.js:140:18)
>> |     at node.js:1043:3
>> |
>> | Traceback (most recent call last):
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
>> <module>
>> |     main(sys.argv[1:])
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
>> main
>> |     manifest_out_path = _vulcanize(args.input, args)
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
>> _vulcanize
>> |     ] + in_html_args)
>> |   File "../../third_party/node/node.py", line 28, in RunNode
>> |     raise
>> | TypeError: exceptions must be old-style classes or derived from
>> BaseException, not NoneType
>> | [468/30779] python ../../chrome/browser/resources/vulcanize_gn.py
>> --host
>> history --input ../../chrome/browser/resources/md_history --out_folder
>> gen/chrome/browser/resources/md_history --depfile
>> gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
>> lazy_load.html --html_out_files app.vulcanized.html
>> lazy_load.vulcanized.html --js_out_files app.crisper.js
>> lazy_load.crisper.js --exclude chrome://resources/html/util.html
>> chrome://history/constants.html
>> | FAILED: gen/chrome/browser/resources/md_history/app.vulcanized.html
>> gen/chrome/browser/resources/md_history/lazy_load.vulcanized.html
>> gen/chrome/browser/resources/md_history/app.crisper.js
>> gen/chrome/browser/resources/md_history/lazy_load.crisper.js
>> | python ../../chrome/browser/resources/vulcanize_gn.py --host history
>> --input ../../chrome/browser/resources/md_history --out_folder
>> gen/chrome/browser/resources/md_history --depfile
>> gen/chrome/browser/resources/md_history/build.d --html_in_files app.html
>> lazy_load.html --html_out_files app.vulcanized.html
>> lazy_load.vulcanized.html --js_out_files app.crisper.js
>> lazy_load.crisper.js --exclude chrome://resources/html/util.html
>> chrome://history/constants.html
>> | ../../third_party/node/linux/node-linux-x64/bin/node
>> ../../third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler
>> --exclude chrome://resources/html/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude
>> chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude
>> chrome://resources/polymer/v1_0/web-animations-js/web-animat
>> ions-next-lite.min.js
>> --exclude chrome://resources/css/roboto.css --exclude
>> chrome://resources/css/text_defaults.css --exclude
>> chrome://resources/css/text_defaults_md.css --exclude
>> chrome://resources/js/load_time_data.js --inline-css --inline-scripts
>> --rewrite-urls-in-templates --strip-comments --redirect
>> "chrome://resources/cr_components/|../../ui/webui/resources/
>> cr_components"
>> --redirect
>> "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements"
>> --redirect "chrome://resources/css/|../../ui/webui/resources/css"
>> --redirect "chrome://resources/html/|../../ui/webui/resources/html"
>> --redirect "chrome://resources/js/|../../ui/webui/resources/js"
>> --redirect
>> "chrome://resources/polymer/v1_0/|../../third_party/polymer/
>> v1_0/components-chromium"
>> --exclude chrome://resources/html/util.html --exclude
>> chrome://history/constants.html --exclude strings.js --exclude
>> chrome://history/strings.js --manifest-out
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/out/
>> Release/gen/chrome/browser/resources/md_history/history_requestlist.txt
>> --root
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> chrome/browser/resources/md_history
>> --redirect
>> "chrome://history/|/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/chromium
>> -62.0.3202.94/chrome/browser/resources/md_history"
>> --out-dir gen/chrome/browser/resources/md_history/bundled --shell
>> app.html
>> --in-html app.html --in-html lazy_load.html failed:
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/chromium-62.0.3202.94/
>> third_party/node/node_modules/polymer-bundler/lib/bin/
>> polymer-bundler.js:178
>> |         const [prefix, path] = redirect.split('|');
>> |               ^
>> |
>> | SyntaxError: Unexpected token [
>> |     at exports.runInThisContext (vm.js:53:16)
>> |     at Module._compile (module.js:373:25)
>> |     at Object.Module._extensions..js (module.js:416:10)
>> |     at Module.load (module.js:343:32)
>> |     at Function.Module._load (module.js:300:12)
>> |     at Function.Module.runMain (module.js:441:10)
>> |     at startup (node.js:140:18)
>> |     at node.js:1043:3
>> |
>> | Traceback (most recent call last):
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 252, in
>> <module>
>> |     main(sys.argv[1:])
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 235, in
>> main
>> |     manifest_out_path = _vulcanize(args.input, args)
>> |   File "../../chrome/browser/resources/vulcanize_gn.py", line 159, in
>> _vulcanize
>> |     ] + in_html_args)
>> |   File "../../third_party/node/node.py", line 28, in RunNode
>> |     raise
>> | TypeError: exceptions must be old-style classes or derived from
>> BaseException, not NoneType
>> | [469/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
>> -mfloat-abi=hard
>> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-
>> beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
>> -MMD -MF obj/base/base/shared_memory_tracker.o.d -DUSE_SYMBOLIZE
>> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
>> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
>> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
>> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
>> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
>> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
>> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
>> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/
>> glib-2.0/include
>> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
>> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
>> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
>> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
>> -Wno-missing-field-initializers -Wno-unused-parameter
>> -fomit-frame-pointer
>> -g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
>> -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
>> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src
>> /debug/chromium/62.0.3202.94-r0
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-
>> sysroot-native=
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
>> -g1 -c ../../base/memory/shared_memory_tracker.cc -o
>> obj/base/base/shared_memory_tracker.o
>> | [470/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
>> -mfloat-abi=hard
>> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-
>> beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
>> -MMD -MF obj/chrome/common/ini_parser/ini_parser.o.d
>> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
>> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
>> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
>> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
>> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
>> -DDYNAMIC_ANNOTATIONS_ENABLED=0
>> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
>> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/
>> glib-2.0/include
>> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
>> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
>> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
>> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
>> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
>> -fdata-sections -ffunction-sections -fomit-frame-pointer -g0
>> -fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
>> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src
>> /debug/chromium/62.0.3202.94-r0
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-
>> sysroot-native=
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
>> -g1 -c ../../chrome/common/ini_parser.cc -o
>> obj/chrome/common/ini_parser/ini_parser.o
>> | [471/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
>> -mfloat-abi=hard
>> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-
>> beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
>> -MMD -MF
>> obj/chrome/app/shutdown_signal_handlers/shutdown_signal_
>> handlers_posix.o.d
>> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
>> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
>> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
>> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
>> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
>> -DDYNAMIC_ANNOTATIONS_ENABLED=0
>> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
>> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/
>> glib-2.0/include
>> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
>> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
>> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
>> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
>> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
>> -fdata-sections -ffunction-sections -fomit-frame-pointer -g0
>> -fvisibility=hidden -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
>> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src
>> /debug/chromium/62.0.3202.94-r0
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-
>> sysroot-native=
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
>> -g1 -c ../../chrome/app/shutdown_signal_handlers_posix.cc -o
>> obj/chrome/app/shutdown_signal_handlers/shutdown_signal_handlers_posix.o
>> | [472/30779] arm-beld-linux-gnueabi-g++  -march=armv7-a -marm -mfpu=neon
>> -mfloat-abi=hard
>> --sysroot=/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-
>> beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot
>> -MMD -MF obj/base/base/activity_analyzer.o.d -DUSE_SYMBOLIZE
>> -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1
>> -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DDISABLE_NACL
>> -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
>> -DOFFICIAL_BUILD -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64
>> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS
>> -D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
>> -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DBASE_IMPLEMENTATION
>> -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
>> -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -I../.. -Igen
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/include/glib-2.0
>> -I/opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linu
>> x-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot/usr/lib/
>> glib-2.0/include
>> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
>> -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
>> -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -Wno-psabi
>> -Wno-unused-local-typedefs -Wno-maybe-uninitialized
>> -Wno-missing-field-initializers -Wno-unused-parameter
>> -fomit-frame-pointer
>> -g0 -fvisibility=hidden -O2 -fno-ident -fdata-sections -ffunction-sections
>> -std=gnu++14 -Wno-narrowing -fno-rtti -fno-exceptions
>> -fvisibility-inlines-hidden  -O2 -pipe -feliminate-unused-debug-types
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0=/usr/src
>> /debug/chromium/62.0.3202.94-r0
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-
>> sysroot-native=
>> -fdebug-prefix-map=/opt/yocto/pyro/build/tmp/work/armv7ahf-n
>> eon-imx-beld-linux-gnueabi/chromium/62.0.3202.94-r0/recipe-sysroot=
>> -g1 -c ../../base/debug/activity_analyzer.cc -o
>> obj/base/base/activity_analyzer.o
>> | [473/30779] python
>> ../../tools/metrics/histograms/generate_expired_histograms_array.py
>> -nchrome_metrics -ogen -Hchrome/browser/metrics/expir
>> ed_histograms_array.h
>> ../../tools/metrics/histograms/histograms.xml
>> ../../tools/metrics/histograms/enums.xml
>> | ninja: build stopped: subcommand failed.
>> | WARNING:
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/temp/run.do_compile.13059:1
>> exit 1 from 'ninja -v -j 8 chrome chrome_sandbox chromedriver'
>> | ERROR: Function failed: do_compile (log file is located at
>> /opt/yocto/pyro/build/tmp/work/armv7ahf-neon-imx-beld-linux-
>> gnueabi/chromium/62.0.3202.94-r0/temp/log.do_compile.13059)
>> ERROR: Task
>> (/opt/yocto/pyro/meta-browser/recipes-browser/chromium/chrom
>> ium_62.0.3202.94.bb:do_compile)
>> failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 3903 tasks of which 3721 didn't need to be
>> rerun and 1 failed.
>>
>> Summary: 1 task failed:
>>
>> /opt/yocto/pyro/meta-browser/recipes-browser/chromium/chromi
>> um_62.0.3202.94.bb:
>> do_compile
>> Summary: There were 12 WARNING messages shown.
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>
>>
>> Which tag/commit is know to build correctly ?
>>
>> Thank you !
>>
>> Best regards
>>
>> On Wed, Nov 15, 2017 at 8:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> > >> As for musl: like I said in my original email and on GitHub, the musl
>> > >> build is currently broken. Carrying tons of patches in the recipe is
>> an
>> > >> uphill battle, so unless someone takes the time to work with
>> upstream I
>> > >> don't think it makes much sense to try to keep the build working.
>> > >
>> >
>> > musl is relatively newer and support for various components may not be
>> > upstream
>> > but it is getting there. There is no alternative than to carry patches
>> > as of now.
>> > and keep forward porting them as the versions advance. We may never get
>> all
>> > of them upstreamed as is the case with many other large packages.
>> >
>> > > OK, fair enough, maybe Khem will again chime in and fix it for musl
>> (in
>> > > the meantime we might blacklist it for musl that people don't wait for
>> > > the build to fail).
>> >
>> > The patches needs to be redone mostly. Its ok to blacklist it from now.
>> > I wish someone besides me would have cared too.
>> > --
>> > _______________________________________________
>> > Openembedded-devel mailing list
>> > Openembedded-devel@lists.openembedded.org
>> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>> >
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Otavio Salvador]

On Tue, Nov 28, 2017 at 6:13 AM, Ayoub Zaki <ayoub.zaki@googlemail.com> wrote:
> Thank you, indeed I used rocko branches and it seems to build and also run
> on an iMX6!
> I use a mainline kernel 4.14  and with iMX6 Etnaviv GPU acceleration
> support.
> It's not clear for me how to enable GPU acceleration with chromium +
> Etnaviv :
> I tried the switch --use-gl=any,  it starts up but when running WebGL demo
> Chromium/Etnaviv is crashing...
> For normal browsing it works just fine however I noticed that CPU
> consumption is very high > 50%
> Anyone having better experience with Chromium + HW accleration support on
> iMX6 ?

The i.MX6 support requires a number of patches to properly support its
hardware. Currently not well supported ...

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ayoub Zaki]

Hi Otavio,

that's a shame :-( thanks for the information.
are they other browsers that are well supported with GPU acceleration on
iMX6 ?
what about Firefox ?
Thank you!

On Tue, Nov 28, 2017 at 12:58 PM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> On Tue, Nov 28, 2017 at 6:13 AM, Ayoub Zaki <ayoub.zaki@googlemail.com>
> wrote:
> > Thank you, indeed I used rocko branches and it seems to build and also
> run
> > on an iMX6!
> > I use a mainline kernel 4.14  and with iMX6 Etnaviv GPU acceleration
> > support.
> > It's not clear for me how to enable GPU acceleration with chromium +
> > Etnaviv :
> > I tried the switch --use-gl=any,  it starts up but when running WebGL
> demo
> > Chromium/Etnaviv is crashing...
> > For normal browsing it works just fine however I noticed that CPU
> > consumption is very high > 50%
> > Anyone having better experience with Chromium + HW accleration support on
> > iMX6 ?
>
> The i.MX6 support requires a number of patches to properly support its
> hardware. Currently not well supported ...
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Otavio Salvador]

On Tue, Nov 28, 2017 at 10:47 AM, Ayoub Zaki <ayoub.zaki@googlemail.com> wrote:
> Hi Otavio,
>
> that's a shame :-( thanks for the information.
> are they other browsers that are well supported with GPU acceleration on
> iMX6 ?
> what about Firefox ?

GPU works, VPU does not. You need to pass some params to ignore
gpu-blacklist and like.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ian Coolidge]

The chromium-imx patches don't apply cleanly since chromium52. Also
patching chromium52 properly to compile and use chromium-imx on Rocko also
has it's issues, I've got a build for that currently but SSL handshaking is
broken somehow. I need to debug it more but its a large task.

On Tue, Nov 28, 2017 at 5:05 AM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> On Tue, Nov 28, 2017 at 10:47 AM, Ayoub Zaki <ayoub.zaki@googlemail.com>
> wrote:
> > Hi Otavio,
> >
> > that's a shame :-( thanks for the information.
> > are they other browsers that are well supported with GPU acceleration on
> > iMX6 ?
> > what about Firefox ?
>
> GPU works, VPU does not. You need to pass some params to ignore
> gpu-blacklist and like.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Raphael Kubo da Costa]

Ayoub Zaki <ayoub.zaki@googlemail.com> writes:

> Hello all,
>
> I'm trying to build from the latest commit meta-browser:
> a8bb1e779bc3565beacceadc4414816670f33475 with an imx6 using yocto pyro
> branch with meta-freescale, however the build fails :

FWIW, the errors reported below seem to be coming from Node. I guess the
node.js version in your pyro branch is too old and does not support all
the JS features present in the Chromium code.

Re: [meta-browser] CFT: Chromium 62 in meta-browser

[Ayoub Zaki]

Hi Raphael,

Yes you are right, it  built better with using rocko branch, now Chromium
is up and running.
Thanks  again for the amazing work :-)

best regards,

On Mon, Dec 11, 2017 at 12:30 PM, Raphael Kubo da Costa <
raphael.kubo.da.costa@intel.com> wrote:

> Ayoub Zaki <ayoub.zaki@googlemail.com> writes:
>
> > Hello all,
> >
> > I'm trying to build from the latest commit meta-browser:
> > a8bb1e779bc3565beacceadc4414816670f33475 with an imx6 using yocto pyro
> > branch with meta-freescale, however the build fails :
>
> FWIW, the errors reported below seem to be coming from Node. I guess the
> node.js version in your pyro branch is too old and does not support all
> the JS features present in the Chromium code.
>