mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-09-02 10:55:38 +02:00
8291505ccd
The v73 version tries to build and run a test program at compile time to check whether compiler supports sizeof and expression statements and sets HAVE_STATEMENT_EXPR accordingly. This requires EXEWRAPPER_ENABLED in meson.bbclass to be True and qemu-usermode to be working. In cases when EXEWRAPPER_ENABLED is False, build fails with error: | ../git/meson.build:213:0: ERROR: Can not run test applications in this cross environment. We don't really need to do this as these have been supported since gcc3 and can set the configs to 1. The autotools implementation also used to set it to 1 so this doesn't change anything: https://github.com/pmem/ndctl/blob/v72.1/configure.ac#L70 Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
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. Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' 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>