But it looks like the android_arm.release build chokes on linking statically...
LINK(target) .../v8/build-3.15.11/out/android_arm.release/preparser .../android-ndk-r8d/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: error: .../android-ndk-r8d/platforms/android-9/arch-arm/usr/lib/libc.a(atexit.o): multiple definition of 'atexit' .../android-ndk-r8d/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: .../android-ndk-r8d/platforms/android-9/arch-arm/usr/lib/crtbegin_dynamic.o: previous definition here .../android-ndk-r8d/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: error: cannot find -ldl .../android-ndk-r8d/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-androideabi/bin/ld: .../android-ndk-r8d/sources/cxx-stl/stlport//libs/armeabi-v7a/libstlport_static.a(helper_func_internal.o): in function __cxxabiv1::fatalError(char const*):helper_func_internal.cc(.text+0x4f2): error: undefined reference to 'dlopen' ( and more) On Thu, Jan 10, 2013 at 1:37 PM, Joe Millenbach <[email protected]> wrote: > FWIW, we want to statically link as we want the same test to run on > multiple systems. Different versions of libraries can have or lack > optimizations that change the result of benchmarks, or be missing as > the systems we're running on vary a lot and we don't have control over > making them match. But that link is good information to have. > > My hope at a trivial code change disappeared quickly when I tried to > turn on my new setting. I'll have to learn GYP and really understand > how to enable this option on all the variants (OSX, Windows) in > addition to the couple I planned to use (Linux and Android). > > The idea of using link flags environment variables (LDFLAGS=-static > make ...) seemed to create a functional binary that was a little > bigger than the dynamic version, in my brief test. There was a > comment at the end that worried me a little (a similar message appears > a few times throughout)... > > platform-posix.cc:(.text._ZN2v88internal11POSIXSocket7ConnectEPKcS3_+0x8d): > warning: Using 'getaddrinfo' in statically linked applications > requires at runtime the shared libraries from the glibc version used > for linking > > And I haven't tried moving my executables around to test how stable or > functional they really are. I know when I tried to run .check it > failed for about 90% of the tests, but I'm not sure how fool proof > those are. > > On Thu, Jan 10, 2013 at 9:12 AM, Matt Horsnell > <[email protected]> wrote: >> With the old scons build system you used to be able to build statically, >> what changed? >> >> On Thursday, 10 January 2013 12:43:33 UTC, mschwartz wrote: >>> >>> Comments 6 & 7 in your link are particularly interesting. The link in >>> comment 6 is a must read for anyone considering static linking on Linux. >>> >>> On Jan 10, 2013, at 4:27 AM, Stephan Beal <[email protected]> wrote: >>> >>> On Thu, Jan 10, 2013 at 7:58 AM, Joe Millenbach <[email protected]> >>> wrote: >>>> >>>> If I make a patch that added the option, could it be accepted? Or is >>>> this functionality that is not desired? >>> >>> >>> FWIW: v8 uses networking classes in some of the debugging code, and on >>> Linux the networking libraries cannot be linked statically (for voodoo >>> reasons which i don't recall). This ticket suggests that one might also have >>> problems when statically linking against pthreads on linux: >>> http://sourceware.org/bugzilla/show_bug.cgi?id=10652 >>> >>> -- >>> ----- stephan beal >>> http://wanderinghorse.net/home/stephan/ >>> http://gplus.to/sgbeal >>> >>> -- >>> v8-users mailing list >>> [email protected] >>> http://groups.google.com/group/v8-users >>> >>> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
