buildroot/package/gcc/gcc-initial, branch 2019.02-op-build

package/gcc: remove unused HOST_GCC_FAKE_TESTSUITE

2018-12-10T10:48:22+00:00

HOST_GCC_FAKE_TESTSUITE was removed since commit [1]. [1] 545ca6a0f2f4e0d8b3812949476ac2856264b83c Signed-off-by: Romain Naour Signed-off-by: Thomas Petazzoni

package/gcc: remove BR2_GCC_SUPPORTS_FINEGRAINEDMTUNE

2018-10-21T14:26:59+00:00

Since commit 8f8e9162fae5fdc1788dcf33f02b20ddaa5e6846 ("package/gcc: do not mourn avr32 for too long..."), in which we dropped AVR32 support, the BR2_GCC_SUPPORTS_FINEGRAINEDMTUNE is always 'y'. Therefore, it is totally useless to keep this option around, and this commit removes it, making the corresponding code unconditional along the way. Signed-off-by: Thomas Petazzoni Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

package: share downloaded files for big packages

2018-04-02T15:48:56+00:00

Theses packages are given as an example of the use of the *_DL_SUBDIR feature. There maybe other packages that would benefit from that feature, they would need to be added on a case by case basis. Signed-off-by: "Yann E. MORIN" Signed-off-by: Maxime Hadjinlian Cc: Maxime Hadjinlian Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard

arch/xtensa: accept the overlay to be an URL

2017-07-09T14:58:03+00:00

It can be interesting to get the overlay from a remote server, rather than expect it to be present locally. Since that file can be any URL, we can't know its hash, so we just exclude it. Signed-off-by: "Yann E. MORIN" Signed-off-by: Max Filippov [Thomas: use DL_DIR instead of BR2_DL_DIR.] Signed-off-by: Thomas Petazzoni

arch/xtensa: allow specifying path to tarball file

2017-07-09T13:41:51+00:00

currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" Cc: Gustavo Zacarias Signed-off-by: Max Filippov Signed-off-by: Thomas Petazzoni

package/gcc: use the Xtensa variables

2017-03-26T13:49:45+00:00

... instead of re-computing them over-and-over-again. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Max Filippov Signed-off-by: Thomas Petazzoni

gcc: the special workaround for ARC is no longer required

2016-11-23T22:16:41+00:00

It seems with the change to gcc 6.x based toolchain this workaround is no longer required. Tested with an arc hs toolchain. Signed-off-by: Waldemar Brodkorb Acked-by: Alexey Brodkin Signed-off-by: Thomas Petazzoni

toolchain/wrapper: fix 'reinstall'

2016-10-24T21:02:33+00:00

toolchain-wrapper was not reinstalled. So rules toolchain-external-reinstall, gcc-initial-reinstall, gcc-final-reinstall didn't work as expected. In add, normalize variable name: s/TOOLCHAIN_BUILD_WRAPPER/TOOLCHAIN_WRAPPER_BUILD/ Signed-off-by: Jérôme Pouiller Signed-off-by: Thomas Petazzoni

gcc: rename option for ARC gcc

2016-09-20T19:19:24+00:00

The ARC gcc version is now based on gcc 6.x and no longer gcc 4.8.x, which makes the option BR2_GCC_VERSION_4_8_ARC a bit irrelevant, as is the prompt of this option. This commit therefore renames this option to BR2_GCC_VERSION_ARC, and adjust its prompt as well. Signed-off-by: Thomas Petazzoni

gcc: use _EXCLUDES, not _TAR_EXCLUDES

2015-11-04T07:32:39+00:00

As reported by Steven Noonan, the variable recently introduced in the package infrastructure to exclude certain parts of an archive from being extracted is _EXCLUDES, not _TAR_EXCLUDES. However, the gcc code was incorrectly using _TAR_EXCLUDES. This commit fixes that. Signed-off-by: Thomas Petazzoni Reported-by: Steven Noonan