Peter Korsgaard e478ad1e5d gcc: or1k: use 20170218 tag instead of branch ... 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 <peter@korsgaard.com> Tested-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>		2018-02-05 08:30:38 +01:00
..
4.9.4	package/gcc: fix build issue with glibc 2.26	2017-09-27 22:52:14 +02:00
5.5.0	package/gcc: bump to 5.5.0	2017-10-17 22:40:42 +02:00
6.4.0	package/gcc: fix build issue with glibc 2.26	2017-09-27 22:52:14 +02:00
7.3.0	package/gcc: bump 7.x series to 7.3.0	2018-01-28 20:26:22 +01:00
arc-2017.09-release	fwup: fix for ARC toolchain	2017-11-17 21:49:16 +01:00
gcc-final
gcc-initial
or1k-musl-5.4.0-20170218	gcc: or1k: use 20170218 tag instead of branch	2018-02-05 08:30:38 +01:00
Config.in.host	gcc: or1k: use 20170218 tag instead of branch	2018-02-05 08:30:38 +01:00
gcc.hash	gcc: or1k: use 20170218 tag instead of branch	2018-02-05 08:30:38 +01:00
gcc.mk	gcc: allow the selection of upstream GCC 7.x for ARC	2017-11-29 23:20:53 +01:00