On Tue, 2018-01-02 at 12:00 -0800, Joe Slater wrote:
> postinstall scripts may run target binaries and need to know
> where shared libraries are.
>
> Signed-off-by: Joe Slater <jsla...@windriver.com>
> ---
> meta/classes/allarch.bbclass | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/classes/allarch.bbclass b/meta/classes/allarch.bbclass
> index 51ba509..3749328 100644
> --- a/meta/classes/allarch.bbclass
> +++ b/meta/classes/allarch.bbclass
> @@ -11,9 +11,8 @@ python () {
> # No need for virtual/libc or a cross compiler
> d.setVar("INHIBIT_DEFAULT_DEPS","1")
>
> - # Set these to a common set of values, we shouldn't be using them
> other that for WORKDIR directory
> - # naming anyway
> - d.setVar("baselib", "lib")
> + # Set these to a common set of values, we shouldn't be using them
> other than for WORKDIR directory
> + # naming anyway. Do not set baselib because postinstall may need to
> know where shared libraries are.
> d.setVar("TARGET_ARCH", "allarch")
> d.setVar("TARGET_OS", "linux")
> d.setVar("TARGET_CC_ARCH", "none")
Sorry, but I don't think this can work :/.
Do the sstate sig selftests pass with this change?
I appreciate this will make some things "work" but it will mean that
allarch packages rebuild for each architecture or multilib and that
isn't right either.
So we need a better solution here. Why do we need libdir paths to run
binaries anyway? Is this a libexec issue? Perhaps the things in
question shouldn't be allarch?
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
