mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-06-14 05:49:57 +00:00
Thomas Perrot
64bc3a36e4
Otherwise, when ccache is enabled the following error occurs, by adding CCACHE_DISABLE = "1" in the recipe this is avoided. | No installed jimsh or tclsh, building local bootstrap jimsh0 | Host System...x86_64-pc-linux-gnu | Build System...x86_64-pc-linux-gnu | C compiler...ccache ccache gcc -isystem/src/build/tmp/work/x86_64-linux/openocd-native/0.10+gitrAUTOINC+ded6799025-r0/recipe-sysroot-native/usr/include -O2 -pipe | C++ compiler...ccache ccache g++ -isystem/src/build/tmp/work/x86_64-linux/openocd-native/0.10+gitrAUTOINC+ded6799025-r0/recipe-sysroot-native/usr/include -O2 -pipe | Build C compiler...ccache gcc | Checking for stdlib.h...not found | Error: Compiler does not work. See config.log | Try: 'configure --help' for options | configure: error: ./configure.gnu failed for jimtcl | WARNING: exit code 1 from a shell command. | Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
meta-oe ======= This layer depends on: URI: git://github.com/openembedded/openembedded-core.git branch: master revision: HEAD 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 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>