]> code.ossystems Code Review - openembedded-core.git/commit
gcc-sanitizers: Move content from gcclibdir into libdir
authorMike Crowe <mac@mcrowe.com>
Sun, 28 Feb 2021 12:20:54 +0000 (12:20 +0000)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 2 Mar 2021 14:15:27 +0000 (14:15 +0000)
commit862b4fac3ee7d951758c8c93462331ad52bf0190
tree3542ac003d663c2e93202ba5869363b547eab2cd
parente4604b40075c56a610068179c401537551c93569
gcc-sanitizers: Move content from gcclibdir into libdir

In e9e5744ba8b0d43c8b874d365f83071ce20bf0a1, 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

I think that the same thing needs to happen in gcc-sanitizers.inc,
otherwise I get errors like:

| .../recipe-sysroot/usr/include/gpg-error-64.h:884:11: fatal error: sanitizer/lsan_interface.h: No such file or directory

when attempting to compile with sanitizers enabled.

FILES_${PN} needs updating to match too.

Signed-off-by: Mike Crowe <mac@mcrowe.com>
Cc: Khem Raj <raj.khem@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/gcc/gcc-sanitizers.inc