I've got this error below on one of my build machines, and on close
inspection, it looks like qtwebengine/chromium/v8 requires host side C++
headers in 32-bit besides normal 64-bit version, i.e. libc++-dev:i386 or
lib32stdc++-dev.
How can we check for this and/or document this requirement?
Logs (notice hosttools/g++ and -m32):
FAILED: v8_snapshot/obj/v8/mkpeephole/bytecodes.o
.../tmp-glibc/hosttools/g++ -MMD -MF
v8_snapshot/obj/v8/mkpeephole/bytecodes.o.d -DV8_DEPRECATION_WARNINGS
-DUSE_UDEV -DUSE_AURA=1 -DUSE_NSS_CERTS=1 -DUSE_OZONE=1 -DNO_TCMALLOC
-DDISABLE_NACL -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DFULL_SAFE_BROWSING
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD
-DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DV8_I18N_SUPPORT -DV8_TARGET_ARCH_ARM
-DCAN_USE_ARMV7_INSTRUCTIONS -DCAN_USE_VFP3_INSTRUCTIONS -DCAN_USE_VFP32DREGS
-DCAN_USE_NEON -DUSE_EABI_HARDFLOAT=1 -Iv8_snapshot/gen
-I../../../../git/src/3rdparty/chromium
-I../../../../git/src/3rdparty/chromium/v8/include -Iv8_snapshot/gen/v8/include
-I../../../../git/src/3rdparty/chromium/v8 -fno-strict-aliasing
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe
-pthread -m32 -msse2 -mfpmath=sse -mmmx -g0 -fvisibility=hidden
-Wno-unused-local-ty
pedefs -Wno-maybe-uninitialized -Wno-missing-field-initializers
-Wno-unused-parameter -O3 -fno-ident -fdata-sections -ffunction-sections
-fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11
-fno-delete-null-pointer-checks -fno-rtti -fno-exceptions -Wno-deprecated
-Wno-narrowing -c
../../../../git/src/3rdparty/chromium/v8/src/interpreter/bytecodes.cc -o
v8_snapshot/obj/v8/mkpeephole/bytecodes.o
In file included from
../../../../git/src/3rdparty/chromium/v8/src/interpreter/bytecodes.h:8:0,
from
../../../../git/src/3rdparty/chromium/v8/src/interpreter/bytecodes.cc:5:
/usr/include/c++/5/cstdint:38:28: fatal error: bits/c++config.h: No such file
or directory
compilation terminated.
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
