diff options
| author | Daniel Klauer <daniel.klauer@gin.de> | 2023-10-04 12:54:03 +0200 |
|---|---|---|
| committer | Armin Kuster <akuster808@gmail.com> | 2023-10-12 09:58:05 -0400 |
| commit | ccbc4478f739267c29ce31e52c2f984d57f2c381 (patch) | |
| tree | 213ce2c6a4e04f8c088fff2677f4bfa749488d4e /meta-python/recipes-devtools/python/python3-cmake/run-cmake-from-path.patch | |
| parent | 75b7d005acae7c87a370473af2d6bfe17bc81dfb (diff) | |
| download | meta-openembedded-ccbc4478f739267c29ce31e52c2f984d57f2c381.tar.gz | |
graphviz: Fix build to not use $prefix as search dir
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>
(cherry picked from commit 883860c40c67544dfe3e2d72732e2d8ef46b6f30)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-cmake/run-cmake-from-path.patch')
0 files changed, 0 insertions, 0 deletions