In case of subsequent builds for machines belonging to the same arch we have to rebuild the klcc-cross wrapper because it is harcoding the path to the headers in machine sysroot. This hack is necessary to avoid to mark the klibc infrastructure as machine-specific.
Signed-off-by: Andrea Adami <andrea.ad...@gmail.com> --- meta-initramfs/recipes-devtools/klibc/klcc-cross_2.0.3.bb | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/meta-initramfs/recipes-devtools/klibc/klcc-cross_2.0.3.bb b/meta-initramfs/recipes-devtools/klibc/klcc-cross_2.0.3.bb index 40a65fd..068b3d5 100644 --- a/meta-initramfs/recipes-devtools/klibc/klcc-cross_2.0.3.bb +++ b/meta-initramfs/recipes-devtools/klibc/klcc-cross_2.0.3.bb @@ -28,3 +28,9 @@ do_package_write_ipk[noexec] = "1" do_package_write_rpm[noexec] = "1" do_package_write_deb[noexec] = "1" do_package_write_tar[noexec] = "1" + +# The linux-libc-headers and klibc custom headers are not machine-specific +# but are installed into machine sysroot. +# Klcc wrapper is hardcoding som eof these paths thus, to keep te recipe +# arch-specific, we force the rebuild of klcc-cross for each machine. +do_compile[vardeps] += "MACHINE" -- 1.8.1.5 _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
