linux/poky.git/meta/recipes-devtools/gcc/gcc-configure-common.inc, branch 3.3_M2

gcc10: Don't default back to -fcommon

2020-08-26T13:33:57+00:00

It has been almost 3 months since the upgrade to gcc 10. Switch back to relying on gcc default configuration (-fno-common). This reverts OE-Core commit 951e859b1e8297970278c539e989b8a6d06a9cb3. (From OE-Core rev: 4ee733e1551d3960a23a600eb71a01cf7a51fa06) Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie

gcc10: Default back to -fcommon

2020-05-14T13:15:11+00:00

For time being change back to -fcommon as default, helps us iron out other issues, eventually this should be removed as we fix the packages to work with -fno-common (From OE-Core rev: 951e859b1e8297970278c539e989b8a6d06a9cb3) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Configure all gccs with --disable-install-libiberty

2020-04-26T13:00:50+00:00

OE uses libiberty from binutils, since its properly compiled as pic archive and applications and other libraries needing libiberty can properly link with it. With this option applied, explicit delete of libiberty headers and libraries is not required in install step, since they wont get installed in first place. (From OE-Core rev: fa8a205c69770d23323c9a06373db958af4b34d3) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc-configure: Enable the use of different symbol versioning

2020-01-19T23:49:39+00:00

While the gnu style for symbol versioning is the most usual, --enable-symvers[=style] can be provided several values, gnu, gnu-versioned-namespace, darwin, darwin-export, and sun, depending on users needs. Introduce the SYMVERS_CONF variable to allow the user to configure the symbol versioning in shared libraries. (From OE-Core rev: f850931173fc210ed25706fd8fbfe0a310f99dfc) Signed-off-by: Alejandro Enedino Hernandez Samaniego Signed-off-by: Richard Purdie

gcc: Fix ldbl-128 support for musl

2019-09-03T08:55:50+00:00

Let the patch trigger based on target triplet instead of passing via configure, this lets gcc compile for 64bit otherwise it ends up with libgcc build errors error: unable to emulate 'TF' (From OE-Core rev: 2259bf5366a9ff654dfaf15baa5df2d943383ce6) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

gcc: Remove Java support variables

2019-04-16T10:10:02+00:00

Java support was removed in upstream gcc 7. (From OE-Core rev: 81551871b183f802ce3c1d0c8fb16479d9671a04) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie

gcc: Drop the -initial versions of the compiler

2018-12-26T11:19:54+00:00

Separated out from the previous commit for clarity, this simply drops all the -inital pieces of gcc which are no longer needed after the previous commit. (From OE-Core rev: d84971928b68efddbdb6344b1021d998c9e26adb) Signed-off-by: Richard Purdie

gcc: Drop gcc-cross-initial and use gcc-cross instead

2018-12-26T11:19:54+00:00

We need a libgcc to build glibc. Tranditionally we therefore build a non-threaded and non-shared compiler (gcc-cross-initial), then use that to build libgcc-initial which is used to build glibc which we can then build gcc-cross and libgcc against. Firstly, we can drop the glibc dependency from gcc-cross, *if* we make two changes: a) specify the minimum glibc version to support in a configure option b) create a dummy limits.h file so that later when glibc creates one, the headers structure has support for it. We can do this with a simple empty file Once gcc-cross is libc independent, we can use it to build both libgcc-initial and then later libgcc. libgcc-initial is tricky as we need to imitate the non-threaded and non-shared case. We can do that by hacking the threading mode back to "single" even if gcc reports "posix" and disable libc presence for the libgcc-intial build. We have to create the dummy limits.h to avoid compiler errors from a missing header. glibc will fail to link with libgcc-initial due to a missing "exception handler" capable libgcc (libgcc_eh.a). Since we know glibc doesn't need any exception handler, we can safely symlink to libgcc.a. With those changes, gcc-cross can be used in all places and we only need one build of gcc for each architecture. For some reason ifunc was being disabled on mips prior to these changes but afterwards became enabled but caused assertion failures. This is therefore disabled until we can debug that. (From OE-Core rev: 62b7308b8c4d2b439a15a4f7cbc6f823077bb0be) Signed-off-by: Richard Purdie

gcc: Introduce a knob to configure gcc to default to PIE

2017-07-08T12:34:45+00:00

GCCPIE flag which is empty by default adds "--enable-default-pie" configure option for harderned distros We do not require to add -fpie -pie flag externally anymore (From OE-Core rev: 1c7e195c94764d680a12a49b870f04cd58860f81) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

meta: Drop further remnants of uclibc support

2017-06-22T08:16:00+00:00

uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: ec03023d2165b49a52b83bac1ea2f0bfded7b852) Signed-off-by: Richard Purdie