diff options
author | Peter Korsgaard <peter@korsgaard.com> | 2018-02-03 21:18:21 +0100 |
---|---|---|
committer | Peter Korsgaard <peter@korsgaard.com> | 2018-02-05 08:30:38 +0100 |
commit | e478ad1e5da84240f5a8dea01e6be56a9c8dca99 (patch) | |
tree | 748eec372b01ee80751529bf6ed3d6739f4cf247 /package/gcc/musl-5.4.0/301-missing-execinfo_h.patch | |
parent | e2c03d54bb11a405255e8a2a0bbb22a7ac80d512 (diff) | |
download | buildroot-e478ad1e5da84240f5a8dea01e6be56a9c8dca99.tar.gz buildroot-e478ad1e5da84240f5a8dea01e6be56a9c8dca99.zip |
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>
Diffstat (limited to 'package/gcc/musl-5.4.0/301-missing-execinfo_h.patch')
-rw-r--r-- | package/gcc/musl-5.4.0/301-missing-execinfo_h.patch | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/package/gcc/musl-5.4.0/301-missing-execinfo_h.patch b/package/gcc/musl-5.4.0/301-missing-execinfo_h.patch deleted file mode 100644 index 2d0e7baa44..0000000000 --- a/package/gcc/musl-5.4.0/301-missing-execinfo_h.patch +++ /dev/null @@ -1,13 +0,0 @@ -Index: b/boehm-gc/include/gc.h -=================================================================== ---- a/boehm-gc/include/gc.h -+++ b/boehm-gc/include/gc.h -@@ -503,7 +503,7 @@ - #if defined(__linux__) || defined(__GLIBC__) - # include <features.h> - # if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1 || __GLIBC__ > 2) \ -- && !defined(__ia64__) -+ && !defined(__ia64__) && !defined(__UCLIBC__) - # ifndef GC_HAVE_BUILTIN_BACKTRACE - # define GC_HAVE_BUILTIN_BACKTRACE - # endif |