summaryrefslogtreecommitdiffstats
path: root/meta-oe/dynamic-layers/meta-python/recipes-extended/mozjs
Commit message (Collapse)AuthorAgeFilesLines
* Convert to new override syntaxMartin Jansa2021-08-031-17/+17
| | | | | | | | | | 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>
* mozjs/0001-Port-build-to-python3.patch: Fix typos in descriptionAndreas Müller2021-07-271-3/+3
| | | | | Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mozjs: Drop using JS_VOLATILE_ARMKhem Raj2021-03-032-0/+112
| | | | | | | | | | | | | | | 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>
* mozjs: improve reproducibilityMingli Yu2021-02-041-0/+2
| | | | | | | Remove the build path from the file js60-config. Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mozjs: fix multilib conflictChangqing Li2020-08-141-0/+8
| | | | | | | | | 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>
* mozjs: specify TMPDIRSlater, Joseph2020-08-111-1/+3
| | | | | | | | | | | | | | | | 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>
* mozjs: Remove workaround for gcc < 4.9Adrian Bunk2020-05-122-43/+0
| | | | | Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* conf/layer.conf: add BBFILES_DYNAMIC and dynamic layersChangqing Li2020-03-1118-0/+7732
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>