summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTor Lillqvist <tml@iki.fi>2013-03-22 07:58:22 +0200
committerTor Lillqvist <tml@iki.fi>2013-03-22 07:58:22 +0200
commit8f53d0d09e426c651c9d8f692775681bf84cbc11 (patch)
treedd7e4adedd3d47f7961ab7b7f50322f08d7903b3
parenta25a1c99c43ce5f257ed03d2dafaaec01efbd1d3 (diff)
Update comment for NDK r8e
Change-Id: I7eab3392c7441ea5ddda59055beedc53b7c5e46c
-rw-r--r--configure.ac13
1 files changed, 7 insertions, 6 deletions
diff --git a/configure.ac b/configure.ac
index ae99a9f01a86..54a4a10615d2 100644
--- a/configure.ac
+++ b/configure.ac
@@ -163,12 +163,13 @@ if test -n "$with_android_ndk"; then
android_cpu=x86
fi
- # Check if there is a (self-built) 64-bit tool-chain. Google does not provide 64-bit binaries of
- # the NDK tool-chain, sigh, but it is easy to build one yourself. Using a 64-bit linker is
- # required if you compile everything with -g. A 32-bit linker just won't manage to link the
- # (app-specific) single huge .so that is built for the apps in android/experimental/*. (A 64-bit
- # ld.gold grows to over 10 gigabytes of virtual space when linking such a .so where all objects
- # have been built with debug information.)
+ # Check if there is a 64-bit tool-chain. Google provides a NDK with 64-bit tool-chain binaries in
+ # NDK r8e, and for earlier NDKs it was possible to build one yourself. Using a 64-bit linker is
+ # required if you compile large parts of the code with -g. A 32-bit linker just won't manage to
+ # link the (app-specific) single huge .so that is built for the apps in android/experimental/* if
+ # there is debug information in a significant part of the object files. (A 64-bit ld.gold grows to
+ # much over 10 gigabytes of virtual space when linking such a .so if all objects have been built
+ # with debug information.)
toolchain_system='*'
if test $build_os = linux-gnu; then
case $build_cpu in