meta-openembedded/meta-oe
Khem Raj 62012af133
deqp-runner: Use linux_raw for getrandom backend on riscv32
Fixes
| error[E0425]: cannot find function `getrandom` in crate `libc`
|   --> /usr/src/debug/deqp-runner/0.20.3/sources-unpack/cargo_home/bitbake/getrandom-0.3.2/src/backends/getrandom.rs:29:15
|    |
| 29 |         libc::getrandom(buf.as_mut_ptr().cast(), buf.len(), 0)
|    |               ^^^^^^^^^ not found in `libc`
|
|     Building [===============>          ] 77/121: thiserror-impl, indexmap,...
|     Building [===============>          ] 78/121: thiserror-impl, indexmap,...
| For more information about this error, try `rustc --explain E0425`.
| error: could not compile `getrandom` (lib) due to 1 previous error
|

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-04-06 21:15:00 -07:00
..
classes version-check.conf: add mechanism for checking version mismatch 2025-04-04 19:18:46 -07:00
conf version-check.conf: add mechanism for checking version mismatch 2025-04-04 19:18:46 -07:00
dynamic-layers thin-provisioning-tools: Fix build on riscv32 2025-04-06 11:06:42 -07:00
files libgpiod: Add gpio-manager/gpio to static IDs 2025-03-15 23:05:31 -07:00
lib/oeqa/selftest/cases
licenses openldap: make license match spdx identifier 2025-02-04 20:25:51 -08:00
recipes-benchmark linpack: fix build with gcc-15.0.1 2025-04-01 20:43:27 -07:00
recipes-bsp flashrom: upgrade 1.4.0 -> 1.5.1 2025-03-25 09:33:51 -07:00
recipes-connectivity thrift: Fix build with gcc-15 2025-04-04 19:18:46 -07:00
recipes-core system-config-keyboard: Drop recipe 2025-04-06 08:47:57 -07:00
recipes-crypto libmcrypt: fix build with gcc-15.0.1 2025-04-01 20:43:27 -07:00
recipes-dbs rocksdb: upgrade 9.0.0 -> 9.10.0 2025-03-11 19:35:32 -07:00
recipes-devtools cbindgen: Fix build on riscv32 2025-04-06 10:57:39 -07:00
recipes-extended valkey: update from 8.0.2 -> 8.1.0 2025-04-02 07:27:48 -07:00
recipes-gnome adw-gtk3: upgrade 5.6 -> 5.7 2025-03-25 09:33:50 -07:00
recipes-graphics deqp-runner: Use linux_raw for getrandom backend on riscv32 2025-04-06 21:15:00 -07:00
recipes-kernel crash: Fix build for 32bit targets 2025-03-26 13:13:47 -07:00
recipes-multimedia mpv: build libmpv by default 2025-03-31 14:42:05 -07:00
recipes-navigation geos: upgrade 3.12.1 -> 3.13.1 2025-03-20 09:04:50 -07:00
recipes-networking/cyrus-sasl Drop unnecessary SRC_URI md5sum from the recipes in meta-oe. 2024-11-05 19:19:22 -08:00
recipes-printing qpdf: upgrade 11.10.1 -> 12.0.0 2025-03-25 14:57:20 -07:00
recipes-security usbguard: Patch for protobuf 30.0 API changes 2025-03-13 09:50:12 -07:00
recipes-shells recipes: Fix variable assignment whitespace 2025-03-20 08:46:56 -07:00
recipes-support unicode-ucd: Rename the license.txt in DL_DIR to avoid conflicts 2025-04-06 08:53:11 -07:00
recipes-test pm-qa: fix build with gcc-15.0.1 2025-04-02 07:27:48 -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