buildroot/package/gcc, branch 2018.02

gcc: or1k: use 20170218 tag instead of branch

2018-02-05T07:30:38+00:00

As pointed out by Joel Stanley: https://patchwork.ozlabs.org/patch/863011/ Github now longer provides the exact same tarball for the or1k musl-5.4.0 tarball, breaking the build. Even more, musl-5.4.0 is the name of a git branch, not a tag. Fix both problems by changing to the or1k-musl-5.4.0-20170218 tag, which points to the exact same git commit. Signed-off-by: Peter Korsgaard Tested-by: Joel Stanley Signed-off-by: Peter Korsgaard

package/gcc: bump 7.x series to 7.3.0

2018-01-28T19:26:22+00:00

Remove upstream patches: 0870-xtensa-fix-PR-target-82181.patch 0893-ARC-Configure-script-to-allow-non-uclibc-based-tripl.patch See: https://www.mail-archive.com/gcc@gcc.gnu.org/msg84336.html Signed-off-by: Romain Naour Signed-off-by: Peter Korsgaard

Merge branch 'next'

2017-12-01T20:56:44+00:00

This merges the next branch accumulated during the 2017.11 release cycle back into the master branch. A few conflicts had to be resolved: - In the DEVELOPERS file, because Fabrice Fontaine was added as a developer for libupnp in master, and for libupnp18 in next. Resolution is simple: add him for both. - linux/Config.in, because we updated the 4.13.x release used by default in master, while we moved to 4.14 in next. Resolution: use 4.14. - package/libupnp/libupnp.hash: a hash for the license file was added in master, while the package was bumped into next. Resolution: keep the hash for the license file, and keep the hash for the newest version of libupnp. - package/linux-headers/Config.in.host: default version of the kernel headers for 4.13 was bumped to the latest 4.13.x in master, but was changed to 4.14 in next. Resolution: use 4.14. - package/samba4/: samba was bumped to 4.6.11 in master for security reasons, but was bumped to 4.7.3 in next. Resolution: keep 4.7.3. Signed-off-by: Thomas Petazzoni

gcc: allow the selection of upstream GCC 7.x for ARC

2017-11-29T22:20:53+00:00

Upstream gcc now has support for ARC, as of 7.x, with 7.2 being usable, so let's allow its selection. GCC from Synopsys GitHub still has a lot of fixes and improvements most of which will be a part of the next upstream release but let's see how it goes and if we see vanilla GCC doesn't require way too many back-ported patches we'll be able to get rid of Synopsys GitHub here at all. As of today the only really required back-port is the one for non-uClibc libc. Back-ported from upstream master with help of: -------------------->8-------------------- git format-patch 927c0132251f -1 -- . ':!gcc/ChangeLog' ':!libgcc/ChangeLog' -------------------->8-------------------- Signed-off-by: Alexey Brodkin Cc: Arnout Vandecappelle (Essensium/Mind) Cc: Thomas Petazzoni Cc: Peter Korsgaard Signed-off-by: Thomas Petazzoni

arch/mips: inverse the NaN logic

2017-11-24T21:39:56+00:00

Currently the possibility to choose the NaN encoding is conditional to having a sufficiently recent gcc version. Which means that the architecture selection depends on the gcc version. But that's opposite to what we've always done in Buildroot: the software versions are conditional to the architecture options. There is nothing we can do about the hardware: it is there, we can't change it, while we can restrict ourselves to using software that is working on said hardware. Thus, we inverse the logic, to move the condition onto the software side: whenever NaN-2008 are selected, we restrict the toolchain selection to at least a gcc-4.9. But now, the option with the NaN type is always set, so we must enclose the code in gcc.mk inside a HAS_NAN_OPTION condition, as is already done for the external toolchain case. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

package/gcc: slight cleanup and reorg in remaining arch depends

2017-11-24T21:20:14+00:00

Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/arm: some variants need different gcc versions

2017-11-24T21:19:14+00:00

Take the conditions currently specified in the gcc version choice. Also, the conditions explained in the commit log for 78c2a9f7 were not all properly applied, especially the a57-a53 combo needs gcc-6, but 78c2a9f7 forgot to add the condition to gcc-4.9. gcc-4.9 was excluded for cortex-a17 and a72, but the CodeSourcery external toolchain, which uses 4.8, was not excluded for those two cores. Now it is. Remove the arch condition from gcc and the external toolchains. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/mips: some variants need different gcc versions

2017-11-24T21:18:18+00:00

We use the conditions currently expressed in the gcc version choice. We leave the musl vs mips64 conditions in gcc, because the "fault" really is on gcc, which does not recognise the mips64+musl tuples, so the fix lies within gcc, and the current conditions are fitting. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

arch/bfin: needs gcc >= 6

2017-11-24T21:17:03+00:00

Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

package/gcc: hide versions too old for the current arch

2017-11-24T21:09:58+00:00

Begin the conversion from hard-coded dependencies on architectures, to architecture-specified version requirement, using the newly introduced BR2_ARCH_NEEDS_GCC_AT_LEAST_XXX symbols. Hard-coded dependencies will be removed progressively, as archs are individually converted over to using the new symbols. We do not change the architecture-specific versions for ARC and OpenRISC, because there is no point in doing so for those, as they use special, non-upstream versions anyway. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Signed-off-by: Thomas Petazzoni