aboutsummaryrefslogtreecommitdiffstats
path: root/testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch
diff options
context:
space:
mode:
authorJakub Jirutka <jakub@jirutka.cz>2017-04-28 15:35:22 +0200
committerJakub Jirutka <jakub@jirutka.cz>2017-04-28 15:36:51 +0200
commitc529e08b39870357e8f10ddd9fb48b4aea2543bd (patch)
treeda282ddd664c1a2da9ea125da7b73566127b6fcb /testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch
parentcc5e775db8b5793ee4f2e1e5372bec6b8e27d58a (diff)
downloadaports-c529e08b39870357e8f10ddd9fb48b4aea2543bd.tar.bz2
aports-c529e08b39870357e8f10ddd9fb48b4aea2543bd.tar.xz
testing/emscripten-fastcomp: update abuild according to llvm4
Diffstat (limited to 'testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch')
-rw-r--r--testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch24
1 files changed, 0 insertions, 24 deletions
diff --git a/testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch b/testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch
deleted file mode 100644
index 7d9dc855b0..0000000000
--- a/testing/emscripten-fastcomp/fix-DynamicLibrary-to-build-with-musl-libc.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-From: Natanael Copa <ncopa@alpinelinux.org>
-Date: Thu, 18 Feb 2016 15:33:21 +0100
-Subject: [PATCH] Fix DynamicLibrary to build with musl libc
-
-stdin/out/err is part of the libc and not the kernel so we check for the
-specific libc that does the unexpected instead of linux.
-
-This is needed for making it build with musl libc.
-
---- a/lib/Support/DynamicLibrary.cpp
-+++ b/lib/Support/DynamicLibrary.cpp
-@@ -140,10 +140,10 @@ void* DynamicLibrary::SearchForAddressOfSymbol(const char *symbolName) {
- #define EXPLICIT_SYMBOL(SYM) \
- if (!strcmp(symbolName, #SYM)) return &SYM
-
--// On linux we have a weird situation. The stderr/out/in symbols are both
-+// On GNU libc we have a weird situation. The stderr/out/in symbols are both
- // macros and global variables because of standards requirements. So, we
- // boldly use the EXPLICIT_SYMBOL macro without checking for a #define first.
--#if defined(__linux__) and !defined(__ANDROID__)
-+#if defined(__GLIBC__)
- {
- EXPLICIT_SYMBOL(stderr);
- EXPLICIT_SYMBOL(stdout);