meta-openembedded/meta-oe
Stefan Wiehler 163506182f
syzkaller: Upgrade to latest tip of trunk
- All patches have been upstreamed
- Add Go module dependencies to allow offline builds since upstream does
  not vendor them into the repo anymore
- In accordance to upstream, disable cgo as we are unable to compile
  with it on all supported architectures; in addition, remove
  -linkshared and -buildmode=pie as it requires external (cgo) linking
  (the latter only on ARM and x86). Binary size hardly matters here as
  syzkaller is unlikely to be shipped in a production environment.
- Add missing metadata and comply with style guide
- Mark musl as incompatible as it does not provide the Memory Protection
  Keys API; in addition, there seems to be no intention from upstream to
  support anything besides glibc

Signed-off-by: Stefan Wiehler <me@sephalon.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-08-14 07:40:08 -07:00
..
classes signing.bbclass: make PEM loading compatible with OpenSC 0.26.0 2025-07-02 09:48:26 -07:00
conf reproducibility: move known non-repro list to layer.conf 2025-06-20 10:34:11 -07:00
dynamic-layers spdm-utils: Move back to meta-oe 2025-08-01 17:23:41 -07: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 libc-bench: Always use libgcc runtime with clang on x86 2025-07-20 21:21:32 -07:00
recipes-bsp flashrom: upgrade 1.5.1 -> 1.6.0 2025-07-30 08:03:05 -07:00
recipes-connectivity gensio: upgrade 2.8.7 -> 2.8.15 2025-07-30 08:03:06 -07:00
recipes-core safec: Upgrade to 3.9.1 2025-08-13 20:38:43 -07:00
recipes-crypto cryptsetup: upgrade 2.7.5 -> 2.8.0 2025-07-07 10:00:53 -07:00
recipes-dbs leveldb: Fix cast warnings seen with clang-21 2025-07-29 12:22:21 -07:00
recipes-devtools protobuf: Delete unused 0001-utf8_range-add-version-marker-to-library-19009.patch 2025-08-13 22:38:16 -07:00
recipes-extended 7zip: upgrade 24.09 -> 25.01 2025-08-13 12:25:37 -07:00
recipes-gnome meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-graphics ktx-software: Disable AVX on x86_64 2025-08-13 20:38:43 -07:00
recipes-kernel oprofile: Adjust ptests for UNPACKDIR changes 2025-08-13 10:09:25 -07:00
recipes-multimedia libplacebo: Fix build with latest python 3.14 2025-08-13 10:09:25 -07:00
recipes-navigation proj: Upgrade to 9.6.2 release 2025-07-12 13:50:02 -07:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing gutenprint: fix a build race-condition 2025-07-04 09:42:10 -07:00
recipes-security usbguard: upgrade 1.1.3 -> 1.1.4 2025-07-30 16:40:03 -07:00
recipes-shells meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-support c-ares: backport a patch for a memory leak 2025-08-10 14:43:21 -07:00
recipes-test syzkaller: Upgrade to latest tip of trunk 2025-08-14 07:40:08 -07:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -07:00
SECURITY.md meta: Add SECURITY.md file to all layers 2024-11-23 09:00:14 -08:00

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