On Mon, 2024-07-15 at 11:37 +0100, Richard Purdie via lists.openembedded.org wrote: > On Mon, 2024-07-15 at 18:20 +0800, Kai wrote: > > On 7/15/24 17:59, Martin Jansa wrote: > > > Hi Kai, > > > > > > are you also seeing these buildpaths warnings from libgfortran? > > > These > > > will be fatal since ERROR_QA update from yesterday: > > > https://git.openembedded.org/openembedded-core/commit/?id=b79b191cc43a45dde2adb61ea349b426cb2461d1 > > > and it probably wasn't detected in AB builds which might not enable > > > fortran. > > Yes, it seems exists for long time. My colleague worked on it for > > several days. But it seems hard to resolve that > > > > host path are somehow set to the intrinsic path. > > > > I'll discuss with him tomorrow and check if we can fix it. > > We're seeing these in automated testing now too. > > I'm wondering if adding -ffile-prefix-map might avoid them. Sadly there > are tools which don't support that option so it isn't an easy thing to > add/test.
To be clear, we saw failures in the fortran selftest however I tracked those down to the way we were calling the compiler and fixed it that way. I did try adding file-prefix-map to the compiler commandline but it didn't help. I'm not sure of the status of prefix remapping in the fortran compiler but it doesn't seem to be quite working properly. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#201918): https://lists.openembedded.org/g/openembedded-core/message/201918 Mute This Topic: https://lists.openembedded.org/mt/106704990/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
