diff options
author | Jakub Jirutka <jakub@jirutka.cz> | 2017-04-22 20:14:54 +0000 |
---|---|---|
committer | Jakub Jirutka <jakub@jirutka.cz> | 2017-04-22 22:16:02 +0200 |
commit | a8066d3a6f4fc8c4426877e8625303b0bd514e95 (patch) | |
tree | 082ced6c9084ba580a9da1bfa0288c8bdebb52b1 /community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch | |
parent | 84a08c0be795ec60005781cc9bfaa9c1ff1a9e1a (diff) | |
download | aports-a8066d3a6f4fc8c4426877e8625303b0bd514e95.tar.bz2 aports-a8066d3a6f4fc8c4426877e8625303b0bd514e95.tar.xz |
community/llvm3.9: move from testing
Diffstat (limited to 'community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch')
-rw-r--r-- | community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch b/community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch new file mode 100644 index 0000000000..d5d7f07b5e --- /dev/null +++ b/community/llvm3.9/llvm-fix-DynamicLibrary-to-build-with-musl-libc.patch @@ -0,0 +1,33 @@ +From d12ecb83d01dcb580dd94f4d57828f33d3eb4c35 Mon Sep 17 00:00:00 2001 +From: Natanael Copa <ncopa@alpinelinux.org> +Date: Thu, 18 Feb 2016 15:33:21 +0100 +Subject: [PATCH 3/3] 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. +--- + lib/Support/DynamicLibrary.cpp | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/lib/Support/DynamicLibrary.cpp b/lib/Support/DynamicLibrary.cpp +index 9a7aeb5..0c1c8f8 100644 +--- 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); +-- +2.7.3 + |