[OE-core] [PATCH] gcc-cross: Explicitly depend on linux-libc-headers

McClintock Matthew-B29882 B29882 at freescale.com
Tue Nov 27 20:08:10 UTC 2012


On Thu, Nov 22, 2012 at 3:36 PM, Richard Purdie
<richard.purdie at linuxfoundation.org> wrote:
> gcc-cross cannot build without linux-libc-headers but doesn't explicitly depend on
> it relying on the implied dependency through libc. With cases where pieces
> can be installed through sstate, we now need this explicit dependency to
> ensure builds with partial sstate work.
>
> Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> ---
> diff --git a/meta/recipes-devtools/gcc/gcc-cross.inc b/meta/recipes-devtools/gcc/gcc-cross.inc
> index 6d160d6..cde08ee 100644
> --- a/meta/recipes-devtools/gcc/gcc-cross.inc
> +++ b/meta/recipes-devtools/gcc/gcc-cross.inc
> @@ -1,6 +1,6 @@
>  inherit cross
>
> -DEPENDS = "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}libc-for-gcc ${NATIVEDEPS}"
> +DEPENDS = "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}libc-for-gcc linux-libc-headers ${NATIVEDEPS}"

How would you suggest not forcing a rebuild of all components if the
linux headers signature changes? During our normal development we
change Linux headers for things that would in no way effect gcc or
even libc. It's painful to watch a complete rebuild occur because of
this.

Just have a different recipe for headers for some components?

-M




More information about the Openembedded-core mailing list