From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Chromium build broken
Date: Sat, 11 Jun 2016 12:11:52 +0200 [thread overview]
Message-ID: <575BE3E8.8060809@mlbassoc.com> (raw)
Building chromium is broken on my i.MX6 target.
Poky/Yocto info:
BB_VERSION = "1.31.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-15.10"
TARGET_SYS = "arm-amltd-linux-gnueabi"
MACHINE = "teton-p0382"
DISTRO = "amltd"
DISTRO_VERSION = "2.1+snapshot-20160611"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU = "hard"
meta = "master:40e789d1fee7f0df2d23230fff38325119ad2935"
meta-teton-imx6-p0382 = "master:5f3d52b357c0b05e7ea5cfc309e04c8c3aad1260"
meta-fsl-arm = "master:00b46e11e32f859a0d2dad5a5d53d5540be9c15e"
meta-fsl-arm-extra = "master:089ce85e2e2dd78e45b773b947643ab8f4e2b965"
meta-browser = "master:825ea9349fe9b7da39f1de0c3e8e15d9d62f2774"
Error:
| ninja: Entering directory
`/local/p0382_2016-01-13/tmp/work/cortexa9hf-neon-mx6qdl-amltd-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/out/Release'
| [1/9316] SOLINK lib/libnative_theme.so
| [2/9316] CXX obj/components/infobars/core/infobars_core.infobar_container.o
| [3/9316] CXX obj/components/infobars/core/infobars_core.infobars_switches.o
| [4/9316] CXX obj/components/infobars/core/infobars_core.infobar.o
| [5/9316] STAMP obj/ui/compositor/compositor.compile_depends.stamp
| [6/9316] CXX obj/ui/compositor/compositor.callback_layer_animation_observer.o
| FAILED: if [ ! -e lib/libnative_theme.so -o ! -e lib/libnative_theme.so.TOC ]; then arm-amltd-linux-gnueabi-g++
-march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9
--sysroot=/local/p0382_2016-01-13/tmp/sysroots/teton-p0382 -shared -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
-Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC -Wl,--disable-new-dtags -L. -Wl,-O1
-Wl,--as-needed -Wl,--gc-sections -o lib/libnative_theme.so -Wl,-soname=libnative_theme.so @lib/libnative_theme.so.rsp
&& { readelf -d lib/libnative_theme.so | grep SONAME ; arm-amltd-linux-gnueabi-nm -gD -f p lib/libnative_theme.so | cut
-f1-2 -d' '; } > lib/libnative_theme.so.TOC; else arm-amltd-linux-gnueabi-g++ -march=armv7-a -marm -mfpu=neon
-mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/local/p0382_2016-01-13/tmp/sysroots/teton-p0382 -shared -Wl,-O1
-Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,now -Wl,-z,relro -Wl,-z,defs -pthread -Wl,-z,noexecstack -fPIC
-Wl,--disable-new-dtags -L. -Wl,-O1 -Wl,--as-needed -Wl,--gc-sections -o lib/libnative_theme.so
-Wl,-soname=libnative_theme.so @lib/libnative_theme.so.rsp && { readelf -d lib/libnative_theme.so | grep SONAME ;
arm-amltd-linux-gnueabi-nm -gD -f p lib/libnative_theme.so | cut -f1-2 -d' '; } > lib/libnative_theme.so.tmp && if ! cmp
-s lib/libnative_theme.so.tmp lib/libnative_theme.so.TOC; then mv lib/libnative_theme.so.tmp lib/libnative_theme.so.TOC
; fi; fi
| obj/ui/native_theme/native_theme.common_theme.o: In function `_GLOBAL__sub_I_common_theme.cc':
| /usr/src/debug/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/ui/native_theme/common_theme.cc:273: undefined reference
to `gfx::kGoogleBlue500'
| /usr/src/debug/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/ui/native_theme/common_theme.cc:273: undefined reference
to `gfx::kGoogleBlue300'
Note: I'm still using GCC/4.9.x with the standard linker (not gold)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2016-06-11 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 10:11 Gary Thomas [this message]
2016-06-16 10:47 ` Chromium build broken Gary Thomas
2016-06-16 11:15 ` Carlos Rafael Giani
2016-06-16 11:23 ` Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=575BE3E8.8060809@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.