On Tue, 2019-08-13 at 07:36 -0700, Khem Raj wrote: > On Tue, Aug 13, 2019 at 7:23 AM Richard Purdie > <richard.pur...@linuxfoundation.org> wrote: > > On Mon, 2019-08-12 at 16:22 -0700, Khem Raj wrote: > > > OE does not use the traditional /usr/lib/gcc prefix to store gcc- > > > runtime > > > it basically is moved into libdir, however some newer files were > > > installed by newer versions of gcc especially libgomp ( omp.h > > > openacc.h ) > > > into gcclibdir, so we have content in both directories, this > > > confuses > > > other tools which are trying to guess the gcc installation and > > > its > > > runtime location, since now we have two directories, the tools > > > either > > > choose one or other and we get inconsistent behavior, e.g. clang > > > for > > > aarch64 uses /usr/lib but same clang for riscv64 chose > > > /usr/lib/gcc > > > > > > This change ensures that OE ends up with single valid location > > > for > > > gcc > > > runtime files > > > > > > Signed-off-by: Khem Raj <raj.k...@gmail.com> > > > --- > > > meta/recipes-devtools/gcc/gcc-runtime.inc | 5 +++++ > > > meta/recipes-devtools/gcc/gcc-runtime_8.3.bb | 3 ++- > > > meta/recipes-devtools/gcc/gcc-runtime_9.1.bb | 3 ++- > > > 3 files changed, 9 insertions(+), 2 deletions(-) > > > > This appears to break mingw: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/925 > > > > seems virtual:nativesdk:/home/pokybuild/yocto-worker/meta- > mingw/build/meta/recipes-devtools/gcc/gcc-runtime_9.1.bb:do_package > > but I cant see which files can you help
They're in the 1b and 2b logs, e.g.: https://autobuilder.yoctoproject.org/typhoon/api/v2/logs/731185/raw Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core