883860c40c
The graphviz configure script used $prefix/include and $prefix/lib search directories, thus bypassing the recipe sysroot, which could lead to build contamination or failures. The added patch (backported from graphviz 9.0.0) fixes this. Due to the $prefix != /usr check in the configure script, this issue only showed up for recipe build variants which use a different prefix value, such as nativesdk-graphviz (prefix = SDKPATHNATIVE/...) or graphviz-native (prefix = STAGING_DIR_NATIVE/...). Using STAGING_DIR_NATIVE is probably not a problem, since it is recipe-specific anyways, but using SDKPATHNATIVE may be a problem, if it happens to exist and contains headers/libraries. Even though this may be unlikely with the default SDKPATH = "/usr/local/oe-sdk-hardcoded-buildpath" value used in bitbake.conf, the problem can still be triggered, especially if the paths like prefix or SDKPATH are customized in a build. Link: https://gitlab.com/graphviz/graphviz/-/issues/2442 Signed-off-by: Daniel Klauer <daniel.klauer@gin.de> 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 ' 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