linux/poky.git/meta/recipes-devtools/gcc/libgfortran.inc, branch yocto-2.4

libgfortran: Add missing fincludes

2017-07-06T13:38:15+00:00

ERROR: libgfortran-6.3.0-r0 do_package: QA Issue: libgfortran: Files/directories were installed but not shipped in any package: /usr/lib/gcc/x86_64-poky-linux/6.3.0/finclude /usr/lib/gcc/x86_64-poky-linux/6.3.0/finclude/ieee_features.mod /usr/lib/gcc/x86_64-poky-linux/6.3.0/finclude/ieee_arithmetic.mod /usr/lib/gcc/x86_64-poky-linux/6.3.0/finclude/ieee_exceptions.mod (From OE-Core rev: 753de3328d36b95c029d2946660f80e083823678) Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libgfortran: Add missing dependency gcc-cross

2017-07-06T13:38:15+00:00

Due to the fact that the recipe uses INHIBIT_DEFAULT_DEPS, we need to manually add the cross compiler as a dependency. (From OE-Core rev: 00fba52c8a6f6383137cf89fc7aa34cc3e2ff45f) Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Ross Burton 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

meta: remove True option to getVar calls

2016-12-16T10:23:23+00:00

getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?$( ?[^,()]*), True$ (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton 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: poison default sysroot path

2014-10-30T13:01:21+00:00

Various pieces of the code assume that the --sysroot option gets passed into the compiler tools. By having a "sane" default, we don't always spot when this occurs and this can later show up as breakage in sstate, or in usage of the external toolchain. We've long since talked about poisoning the default such that it will break unless the correct option is specified. This patch does just that. If this patch causes something to fail to build, it most likely means the various compiler flags and commands are not correctly being passed through to the underlying piece of software and that there is a real problem that needs fixing, its not the fault of this patch. (From OE-Core rev: 04b725511a505c582a3abdf63d096967f0320779) Signed-off-by: Richard Purdie

gcc: recipe whitespace changes

2014-08-15T17:21:49+00:00

Consistent use of whitespace in multi-line assignment, with special focus on OECONF modifications. Quotes on separate lines, four-space indentation, one value per line. (From OE-Core rev: d971db8b2259e4c35b871cccf130fba193849560) Signed-off-by: Peter A. Bigot Signed-off-by: Richard Purdie

binutils/gcc/gdb: Add TARGET_ARCH to PN for all cross recipes

2014-04-30T15:39:06+00:00

This allows them to co-exist together in the native sysroot, with one set of cross tools per target architecture. (From OE-Core rev: a2c5509520d5c3e082f55844e6545d0309565f8f) Signed-off-by: Richard Purdie

gcc: Convert to use hardlinkdir

2014-04-25T16:19:18+00:00

(From OE-Core rev: 204bc1f39030a3c0dd3eadadabb013aca8bb9cc6) Signed-off-by: Richard Purdie