On 10/6/11 9:20 AM, Richard Purdie wrote:
> Changes to baselib by specific machine configuration were resulting
> in sstate cache invalidation, particularly in multilib configurations.
>
> This patch ensures this doesn't happen and native sstate cache files
> are reusable.
Likely throwing in a can of worms here, but for our existing (non-OE based)
work, we generally change the baselib to "lib64" on 64-bit machines. Without
patching native.bbclass, is it possible to do that?
We do this because we ship both 32-bit and 64-bit host tooling for a variety of
host distributions, I expect we'll have to continue doing that as we transition
to an OE-based system.
> Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
> ---
> diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
> index 5e45aed..ba8b0bf 100644
> --- a/meta/classes/native.bbclass
> +++ b/meta/classes/native.bbclass
> @@ -69,6 +69,8 @@ exec_prefix = "${STAGING_DIR_NATIVE}${prefix_native}"
>
> libdir = "${STAGING_DIR_NATIVE}${libdir_native}"
>
> +baselib = "lib"
> +
> # Libtool's default paths are correct for the native machine
> lt_cv_sys_lib_dlsearch_path_spec[unexport] = "1"
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
