| Summary: |
Building webkitgtk fails on beaglebone-yocto machine |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Michael Opdenacker <michael.opdenacker> |
| Component: |
oe-core other | Assignee: |
Ross Burton <ross.burton> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
jon.mason, michael.opdenacker, randy.macleod
|
| Version: |
4.3 | |
|
| Target Milestone: |
5.1 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
Configuring webkitgtk on nanbield and kirstone fails for the "beaglebone-yocto" machine (ARM Cortex A8): | CMake Error at Source/cmake/WebKitFeatures.cmake:321 (message): | ENABLE_JIT conflicts with ENABLE_C_LOOP. You must disable one or the | other. That's because of this line in the recipe: -DENABLE_JIT=${@bb.utils.contains('TUNE_FEATURES', 'callconvention-hard', 'ON', 'OFF', d)}" and the fact that the image is built with "callconvention-hard", which enables ENABLE_JIT, which is incompatible with ENABLE_C_LOOP which seems to be set by default. I tried to modify the recipe (meta/recipes-sato/webkit/webkitgtk_2.40.5.bb) as follows, replacing: EXTRA_OECMAKE:append:armv7a = " -DENABLE_JIT=${@bb.utils.contains('TUNE_FEATURES', 'callconvention-hard', 'ON', 'OFF', d)}" by EXTRA_OECMAKE:append:armv7a = " -DENABLE_JIT=OFF " Configure works then, but then compiling fails after a long time, from an error that is not detailed by "ninja", just mentioning that one of the compile commands returned with a failed status (which cause doesn't seem to appear in the compiler output). The error doesn't happen for the qemu86-64 and qemuarm64 machines. However, doesn't the autobuilder try to build "world" (corresponding to OE-core recipes) for all supported machines?