On Tuesday, 9 April 2013 16:46:37 UTC+1, Rodolph Perfetta wrote: > It doesn't seem to be in V8 generated code so try forcing the build system > to target armv5: > > export CC=gcc -march=armv5 > export CXX=g++ -march=armv5 > then your make command >
Alas, I don't think it's quite that simple. I've spent all day bashing at this and discovered various things: Firstly, when I compile armeabi code under the NDK it uses "-march=armv5te -mtune=xscale -msoft-float". When I compile armeabi-v7a code under the NDK it uses "-march=armv7-a -mfloat-abi=softfp -mfpu=vfpv3-d16". The gyp scripts that generate the makefiles set the options to match the armeabi-v7a, so just setting CC and CXX as you suggest would not work as the compiler will error out as 2 -march's are given. So I hacked the gyp scripts to properly generate makefiles with the relevant flags above, rebuilt and... it still crashes in the same place. There is a note in this very forum saying that 3.17 is the latest version that will support "older than vfpv2" versions, so I backtracked to 3.9, applied a similar set of changes to the gyp scripts, regenerated the makefiles and rebuilt. And it crashes even with that. So at this point, I'm concluding that there is something fundamental in V8 that means it can't be used successfully with armeabi phones and we'll just disable the use of js/forms in MuPDF for devices of this vintage. If someone can prove me wrong, I'd be very grateful! Thanks, Robin -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
