d4c3fdca5f
In case nghttp2 and/or libuv PACKAGECONFIGs are enabled, nodejs will build some binaries for the build system also, linking to native binaries and using headers from the native sysroot. However in case the dependencies are missing from the native sysroot, then it falls back to the build system's sysroot, and use the files that it can find there. If the build system doesn't have nghttp2/libuv installed, then compilation fails: libuv: ../tools/executable_wrapper.h:5:10: fatal error: uv.h: No such file or directory ngtthp2: <...snip...>/build/tmp/hosttools/ld: cannot find -lnghttp2: No such file or directory To avoid falling back to the build system's sysroot, add the missing libuv-native and nghttp2-native dependencies. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.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.
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