On Thu, 2022-06-30 at 16:14 +0200, Tomasz Dziendzielski wrote:
> Would setting dependency to SDKGCCVERSION be more acceptable?
No, it wouldn't. It doesn't address the manjority of my concerns.
> That way native recipes will not depend on target gcc version.
The native recipes shouldn't depend on the SDK gcc version either.
> > I'm guessing what has happened in your case is that a
> > TMPDIR as reused after changing gcc version but something didn't
> > rebuild, probably as ${S} == ${B} and hence ${B} couldn't be
> > cleaned
>
> The problem is not that it didn't rerun the make or didn't clean the
> ${B} or ${S}. After changing GCCVERSION the nativesdk-mgen is taken
> from sstate-cache.
I don't believe that is the issue. I don't have "nativesdk-mgen", but
taking nativesdk-sed as an example:
$ bitbake nativesdk-sed -S none
(to dump the signatures for that recipe)
$ bitbake-dumpsig
tmp/stamps/aarch64-nativesdk-pokysdk-linux/nativesdk-sed/4.8-r0.do_prepare_recipe_sysroot.sigdata.*
shows:
Hash for dependent task
/media/build1/poky/meta/recipes-devtools/gcc/gcc-crosssdk_12.1.bb:do_populate_sysroot
is 4a58e102e0d4e2652a7f960e728b5ae3465a03a9fe6c26135ab6b4dc5b89b951
Hash for dependent task
virtual:nativesdk:/media/build1/poky/meta/recipes-devtools/gcc/gcc-runtime_12.1.bb:do_populate_sysroot
is 3bcf5017659d63c6e744140dde8db8a9e37a412a38924ab5f1031337dec44198
amongst other things.
i.e. the nativesdk recipes *clearly* do have a dependency on the gcc
version used for nativesdk.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167413):
https://lists.openembedded.org/g/openembedded-core/message/167413
Mute This Topic: https://lists.openembedded.org/mt/92064206/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
