Normally binaries are built with debug symbols and then those are stripped out into corresponding -dbg packages for debugging purposes.
Chromium builds in a lot of components and that leads to a large binary size: * with gcc7 it was 3.9GB with debugging info, stripped down to 80MB w/o it * with gcc8 it became 4.3GB and that is larger than 32-bit addressing, so it becomes corrupted and cannot be stripped or executed By disabling generation of the debugging info in the first place, it is now possible to get a working chromium, but w/o the ability to debug it. Signed-off-by: Denys Dmytriyenko <[email protected]> --- meta-arago-distro/recipes-browser/chromium/chromium-wayland_%.bbappend | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-arago-distro/recipes-browser/chromium/chromium-wayland_%.bbappend b/meta-arago-distro/recipes-browser/chromium/chromium-wayland_%.bbappend index d13606d..923db03 100644 --- a/meta-arago-distro/recipes-browser/chromium/chromium-wayland_%.bbappend +++ b/meta-arago-distro/recipes-browser/chromium/chromium-wayland_%.bbappend @@ -8,3 +8,5 @@ OZONE_WAYLAND_EXTRA_PATCHES = " \ USEGOLD = "" DEPENDS += "gperf-native bison-native" + +FULL_OPTIMIZATION = "-O2 -pipe" -- 2.7.4 _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
