linux/poky.git/meta/recipes-devtools/gcc/gcc-sanitizers.inc, branch uninative-2.2

gcc-sanitizers: Package new liblsan objects built with gcc8

2018-05-15T09:56:50+00:00

Fixes installed-vs-shipped QA errors Reported-by: Dan McGregor (From OE-Core rev: b5533d58ebee81fa1e1c061f4f78acc9a1a940df) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gcc-sanitizers: Update supported architectures

2018-04-07T10:44:50+00:00

aarch64 has been supported since GCC 5.1, sparc has been supported since 4.9, and S390 since 7.1. Also mark as broken entirely with musl. (From OE-Core rev: 7d90d2a70f0184ad715e9917d3e7aa096cf98f79) Signed-off-by: Dan McGregor Signed-off-by: Richard Purdie

gcc: Add recipes for gcc-7

2017-06-14T09:23:27+00:00

Switch default compiler to gcc 7 (From OE-Core rev: 03bb12008891cf1a023aaddb6547da6d41d0cab0) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Clean up unnecessary variable confusion

2017-01-26T10:44:27+00:00

SDKPKGSUFFIX could only really be "nativesdk" and TARGET_SYS never contains that so the code manipulating TARGET_SYS is pointless. I suspect this once worked against MULTIMACH_TARGET_SYS which would be a different question but it no longer does. Its been cut and pasted everywhere. This patch cleans up the variable references to make things a little more readable. (From OE-Core rev: 5599cb72d17bce2ba6e2be16ef64d9a388bcfb25) Signed-off-by: Richard Purdie

gcc: Split builddir saving into its own sstate task

2017-01-26T10:44:27+00:00

When we stashed the gcc build directory for use in generating the various runtimes we were being lazy and just used the staging directory. With recipe specific sysroots this means we're copying a large chunk of data around with the cross compiler which we don't really need in most cases. Separate out the data into its own task and inject this into the configure step. We have to do that here since autotools will wipe out ${B} if it thinks we're rebuilding and we therefore have to time its recreation after that. This also takes the opportunity to remove some pointless (as far as I can tell) conditionals from the do_install code. (From OE-Core rev: dcf15ccf3cc9d55e77228ba8d526f967fc9791b4) Signed-off-by: Richard Purdie

gcc-sanitizers: Depend on target gcc

2016-04-29T06:58:43+00:00

Without this the target gcc might not be in the sysroot leading to configure failure. (From OE-Core rev: 329c532db4b2124fa3f4b3ab8c4c6d6c93ca7c2f) Signed-off-by: Jussi Kukkonen Signed-off-by: Richard Purdie

gcc: use relative path for configure script

2016-02-28T11:32:58+00:00

The absolute path (/path/to/configure) caused __FILE__ to be an absolute path. If 'assert' invoked, it uses __FILE__, and build path would be in elf files. In assert.h ... .# define assert(expr) \ ((expr) \ ? __ASSERT_VOID_CAST (0) \ : __assert_fail (__STRING(expr), __FILE__, __LINE__, __ASSERT_FUNCTION)) ... Which triggered buildpaths QA issue: ... | libgcc-5.3.0: File work/core2-64-poky-linux/libgcc/5.3.0-r0/packages-split/ libgcc-dev/usr/lib64/x86_64-poky-linux/5.3.0/libgcc.a in package contained reference to tmpdir [buildpaths] ... Use relative path to run configure can fix the problem. [YOCTO #7058] (From OE-Core rev: b806e4c004a7e10461fe7428fc130a5aa2528039) Signed-off-by: Hongxu Jia Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gcc-sanitizers: link directly against sysroot libstc++

2016-01-07T13:40:15+00:00

Instead of building a shadow libstdc++-v3 directory with symlinks to the sysroot libstdc++-v3.la, fiddle the Makefiles so that it doesn't attempt to link to a in-tree library at all. This fixes builds where .la files are not being installed into the sysroot at all. (From OE-Core rev: f0f814a674faef2160fb8a041b63169c74da108e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: more removals of redunant FILES_${PN}-dbg

2015-12-16T11:56:30+00:00

In some recipes overly-split -dbg packages were merged into PN-dbg. Unless there's a very good reason, recipes should have a single -dev and -dbg package. (From OE-Core rev: a3b000643898d7402b9e57c02e8d10e677cc9722) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gcc-sanitizers: check gcc-build-internal before link

2015-02-15T21:58:25+00:00

The ${STAGING_INCDIR_NATIVE}/gcc-build-internal-$mtarget may not exist when use the external sdk toolchain, we need check before link for it. Fixed: run.do_configure.12538: 149: cd: can't cd to sysroots/x86_64-linux/usr/include/gcc-build-internal-x86_64-wrs-linux (LOCAL REV: NOT UPSTREAM) -- Sent to oe-core on 20150204 (From OE-Core rev: 82166e514438eb1b562f2a4dc2f9f8fecf3f60df) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie