meta-openembedded/meta-oe
Ankur Tyagi 30942cebe8
mozjs-128: Fix build error with arm and musl
Build fails for qemuarm with musl with following error:
mozglue/misc/StackWalk.o: in function `unwind_callback(_Unwind_Context*, void*)':
| /usr/src/debug/mozjs-128/128.5.2/mozglue/misc/StackWalk.cpp:810:(.text._ZL15unwind_callbackP15_Unwind_ContextPv+0x4): undefined reference to `_Unwind_GetIP'

Referenced commit[1] for the fix, also refreshed patches.

[1] bb86629123

Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2026-01-12 08:53:46 -08:00
..
classes meta-oe: image: optionally remove RAW image after sparse image creation 2025-09-15 09:55:16 -07:00
conf botan: Remove ptests execution on rv32 2025-12-31 08:28:50 -08:00
dynamic-layers rwmem: Fix tests to build with musl 2025-12-24 13:18:31 -08:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark fio: ignore CVE-2025-10824 2025-12-16 19:57:32 -08:00
recipes-bsp pointercal: Add HOMEPAGE variable 2025-12-10 08:58:48 -08:00
recipes-connectivity rtorrent: upgrade 0.16.5 -> 0.16.6 2026-01-12 08:53:45 -08:00
recipes-core recipes-core/toybox: Switch SRC_URI to HTTPS for reliable fetch 2026-01-02 22:30:11 -08:00
recipes-crypto cryptsetup: upgrade 2.8.1 -> 2.8.3 2025-12-24 13:18:25 -08:00
recipes-dbs postgresql: upgrade 17.6 -> 17.7 2025-12-16 19:57:32 -08:00
recipes-devtools ctags: upgrade 6.2.20251130.0 -> 6.2.20260104.0 2026-01-12 08:53:42 -08:00
recipes-extended mozjs-128: Fix build error with arm and musl 2026-01-12 08:53:46 -08:00
recipes-gnome gtkmm4: update 2025-12-03 17:39:27 -08:00
recipes-graphics libsdl3-image: upgrade 3.2.4 -> 3.2.6 2026-01-12 08:53:43 -08:00
recipes-kernel libtracefs: upgrade 1.8.2 -> 1.8.3 2026-01-12 08:53:43 -08:00
recipes-multimedia libopus: upgrade 1.5.2 -> 1.6 2025-12-24 13:18:26 -08:00
recipes-navigation gpsd: upgrade 3.27.2 -> 3.27.3 2026-01-12 08:53:42 -08:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing cups-filters: patch CVE-2025-64524 2025-12-10 08:56:12 -08:00
recipes-security bubblewrap: upgrade 0.10.0 -> 0.11.0 2025-12-28 08:14:40 -08:00
recipes-shells dash: upgrade 0.5.13 -> 0.5.13.1 2025-10-21 20:02:39 -07:00
recipes-support spdlog: upgrade 1.16.0 -> 1.17.0 2026-01-12 08:53:45 -08:00
recipes-test cunit: inherit sourceforge-releases class 2025-11-12 09:38:58 -08:00
COPYING.MIT
README.md README.md: Change maintainer from Andreas to Khem for gnome, multimedia, xfce 2025-09-19 12:21:59 -07:00
SECURITY.md

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Layer maintainer: Khem Raj raj.khem@gmail.com