mozjs does not really use X but arcane autoconf 2.13 means its poking at
build host for X headers and libraries. On build hosts where X is
installed this results in wrong paths being searched for target X
headers, this gets caught by configure QA and it fails
ERROR: mozjs-78-78.15.0-r0 do_configure: QA Issue: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.
Rerun configure task after fixing this. [configure-unsafe]
ERROR: mozjs-78-78.15.0-r0 do_configure: Fatal QA errors were found, failing task.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Did not get rid of checks using llvm-objdump. So depend either llvm-native
from oe-core or clang-native from meta-clang
* Unfortunately we still need python3-six(-native) although firefox ships a
version in third_party. If somebody more clever than me can solve this,
mozjs-78 can be moved out of dynamic-layers
* Get rid of erroneous dependency trying to satisfy llvm_objdump
It was tested improperly so configure faile for meta-clang not in layers
It is not necessary for building js only - see mozjs-91
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The libmozjs package was including /usr/lib/libjs_static.ajs, not
required for runtime usage.
Keep this file, but move it to the staticdev package.
Signed-off-by: Kurt Kiefer <kurt.kiefer@arthrex.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The new release requires rust to build and at the same time allows
updating to python 3.10; I took the opportunity to rewrite the
recipe from scratch, drop all the old cruft and use the official,
current upstream build system in it.
All prior patches and tweaks have been dropped; I have no
reasonable way to test them, so if something regressed
for you I'm afraid it needs to be addressed after the fact.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the result of automated script (0.9.1) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
JS_VOLATILE_ARM was a workaround for a gcc 4.7 bug on B2G where it
would generate unaligned word accesses that should have been
individual byte accesses. firefox now a days require at least gcc 6.1+ (and ARM
systems support unaligned accesses). see [1]
in gcc11 volatile wont be accepted as argument qualifier in functions,
hence the build breaks, this patch unbreaks it
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1495731
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Andreas Müller <schnitzeltony@gmail.com>
fix error:
.do_rootfs.2023872:4562: file /usr/bin/js60-config conflicts between attempted installs of mozjs-dev-60.9.0-r0.core2_64 and lib32-mozjs-dev-60.9.0-r0.core2_32
log.do_rootfs.2023872:4563: file /usr/include/mozjs-60/js-config.h conflicts between attempted installs of mozjs-dev-60.9.0-r0.core2_64 and lib32-mozjs-dev-60.9.0-r0.core2_32
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Although it is extremely rare the following type of error
can occur during configuration:
Creating `/tmp/conftest.i53clm4z.cpp` with content:
...
x86_64-wrs-linux-g++: error: /tmp/conftest.i53clm4z.cpp: No such file or directory
x86_64-wrs-linux-g++: error: /tmp/conftest.i53clm4z.cpp: No such file or directory
x86_64-wrs-linux-g++: fatal error: no input files
So, specify a local directory as TMPDIR during configuration.
Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
some recipes under meta-oe have dependency on meta-python,
and test_world of yocto-check-layer will failed with error
like:
ERROR: test_world (common.CommonCheckLayer)
ERROR: Nothing PROVIDES 'python3-pytoml-native' (but
/meta-openembedded/meta-oe/recipes-extended/mozjs/mozjs_60.9.0.bb
DEPENDS on or otherwise requires it). Close matches:
python3-numpy-native
python3-pycairo-native
python3-rpm-native
ERROR: Required build target 'meta-world-pkgdata' has no buildable
providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
'mozjs', 'python3-pytoml-native']
fix by make these recipes only active when identified layers are
present
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Khem Raj
Andreas Müller
Kurt Kiefer
Alexander Kanavin
Martin Jansa
Mingli Yu
Changqing Li
Slater, Joseph
Adrian Bunk