summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Noordhuis <info@bnoordhuis.nl>2016-08-28 12:52:59 +0200
committerBen Noordhuis <info@bnoordhuis.nl>2016-09-05 10:21:34 +0200
commita290ddfdc9cd9453886d433060c5132095d916c4 (patch)
treee5055a641e7e23289d54ac753e940daf66c66952
parenta01e8bcf189bd598d496f347f60007bc2211e528 (diff)
downloadnode-new-a290ddfdc9cd9453886d433060c5132095d916c4.tar.gz
src: unbreak build when compiling against uclibc
It seems that it is possible with some toolchains for both `__GLIBC__` and `__UCLIBC__` to be defined, confusing our "do we have execinfo.h?" logic. Assume that when `__UCLIBC__` is defined, we are dealing with a libc that does not have execinfo.h. Fixes: https://github.com/nodejs/node/issues/8233 PR-URL: https://github.com/nodejs/node/pull/8308 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
-rw-r--r--src/backtrace_posix.cc4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/backtrace_posix.cc b/src/backtrace_posix.cc
index 231cc03000..8fd798757a 100644
--- a/src/backtrace_posix.cc
+++ b/src/backtrace_posix.cc
@@ -4,7 +4,9 @@
#include <features.h>
#endif
-#if defined(__linux__) && !defined(__GLIBC__) || defined(_AIX)
+#if defined(__linux__) && !defined(__GLIBC__) || \
+ defined(__UCLIBC__) || \
+ defined(_AIX)
#define HAVE_EXECINFO_H 0
#else
#define HAVE_EXECINFO_H 1