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

Martin Jansa martin.jansa at gmail.com
Wed Nov 15 14:20:06 UTC 2017


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 at 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 at intel.com> wrote:
>
>> Raphael Kubo da Costa <raphael.kubo.da.costa at 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 at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>



More information about the Openembedded-devel mailing list