Some related info I've found now: https://reviews.llvm.org/D148975?id=516863 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109591
maybe affected by -fcanon-prefix-map used since gcc-13: https://git.openembedded.org/openembedded-core/commit/?id=abe97fa74b10c2c71d79bc3573d4edb509b111f5 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108464#c8 and I was also using ccache which used to have some issues in this area (but the python3-matplotlib issue is IIRC reproducible without ccache as well): https://github.com/ccache/ccache/issues/163 We might need more experiments before this is applied (I'm glad I've sent it only as RFC). I'll try to find some time next week. On Wed, Sep 4, 2024 at 8:42 AM Martin Jansa via lists.openembedded.org <[email protected]> wrote: > > Please be aware that: > https://git.openembedded.org/openembedded-core/commit/?id=593ffffc3baf064b982891d61dacebd08aed3e96 > claims that these options are evaluated right to left (last one first) > and even shows the same issue as what I was seeing as a reason to do > the opposite (move STAGING_DIR_NATIVE after STAGING_DIR_HOST) and I'm > basically reverting that change (which I didn't noticed until today). > > So either the processing order changed since 2018 with gcc-7.3 or > something is wrong (at least the comment above DEBUG_PREFIX_MAP would > be wrong if the processing order was changed). > > Regards, > > On Mon, Sep 2, 2024 at 6:29 PM Martin Jansa via lists.openembedded.org > <[email protected]> wrote: > > > > * and add -fmacro-prefix-map as well > > > > * the default STAGING_DIR_NATIVE starts with STAGING_DIR_HOST and the > > only difference is '-native' suffix at the end > > > > * this can lead into replacing STAGING_DIR_NATIVE path with just -native > > if STAGING_DIR_HOST is listed in DEBUG_PREFIX_MAP before > > STAGING_DIR_NATIVE > > > > * I've noticed this by accident in python3-matplotlib where buildpaths > > QA warning was triggered only for lib32-python3-matplotlib and it was > > because pybind11 path to STAGING_DIR_NATIVE was mapped to only > > '-native/<path>' in python3-matplotlib build (which doesn't trigger > > buildpaths QA and lib32-python3-matplotlib the macro path wasn't > > replaced at all, because of 'lib32-' prefix in: > > > > -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/work/i586-oemllib32-linux/lib32-python3-matplotlib/3.7.2/lib32-recipe-sysroot= > > \ > > > > -fmacro-prefix-map=/OE/build/oe-core/tmp-glibc/work/i586-oemllib32-linux/lib32-python3-matplotlib/3.7.2/lib32-recipe-sysroot= > > \ > > > > -fdebug-prefix-map=/OE/build/oe-core/tmp-glibc/work/i586-oemllib32-linux/lib32-python3-matplotlib/3.7.2/recipe-sysroot-native= > > \ > > > > * more details in meta-python fix for lib32-python3-matplotlib: > > https://lists.openembedded.org/g/openembedded-devel/message/112074 > > > > Signed-off-by: Martin Jansa <[email protected]> > > --- > > Sending as RFC, because I haven't build whole world with this > > and there might be better way to do this or more buildpaths > > issues triggered by this than fixed > > > > meta/conf/bitbake.conf | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf > > index d8252c5b82..ad152ffb6a 100644 > > --- a/meta/conf/bitbake.conf > > +++ b/meta/conf/bitbake.conf > > @@ -653,9 +653,10 @@ DEBUG_PREFIX_MAP ?= "-fcanon-prefix-map \ > > -fdebug-prefix-map=${S}=${TARGET_DBGSRC_DIR} \ > > -fmacro-prefix-map=${B}=${TARGET_DBGSRC_DIR} \ > > -fdebug-prefix-map=${B}=${TARGET_DBGSRC_DIR} \ > > + -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \ > > + -fmacro-prefix-map=${STAGING_DIR_NATIVE}= \ > > -fdebug-prefix-map=${STAGING_DIR_HOST}= \ > > -fmacro-prefix-map=${STAGING_DIR_HOST}= \ > > - -fdebug-prefix-map=${STAGING_DIR_NATIVE}= \ > > " > > DEBUG_LEVELFLAG ?= "-g" > > > > -- > > 2.46.0 > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#204192): https://lists.openembedded.org/g/openembedded-core/message/204192 Mute This Topic: https://lists.openembedded.org/mt/108229773/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
