Martin Storsjö <[email protected]> writes: > I tested it on a raspberry pi (ARMv6), and it seems to work pretty > much as intended - I was able to do a fat build with neon, while > executing the testsuite works (so the detection seems to work as > intended).
Good. > I also tested building for ARMv5 using the android NDK, and I noted > that arm/v6/aes*.asm require a ".arch armv6" at the start, otherwise > they fail to assemble in that configuration. I'll apply that patch. > To test this for yourself in case you're interested, add > <ndk>/toolchains/arm-linux-androideabi-4.6/prebuilt/*x86*/bin to your > path, configure with this line: I have some experience in building things for android. But it's a bit of a hassle to get the testsuite over to a device for testing. > Other than that, building with --enable-fat does seem to do the right > thing - much better than the current setup. (E.g. currently, if > cross-compiling for raspberry pi, it fails to enable the v6 routines, > since the host triplet is arm-bcm2708hardfp-linux-gnueabi even though > it's a armv6 device. When building on such a device, config.guess > gives armv6l-unknown-linux-gnueabihf instead.) To me, that sounds like the crosscompiler setup is a bit strange. It ought to be possible to configure with --host=armv6l-unknown-linux-gnueabihf, and still get the right cross tools, right? > I take it you've tested building for windows? I can cross compile for 32-bit and 64-bit windows, but my wine setup doesn't support 64-bit executables. So testing on x86_64 windows (and macosx) is appreciated. Thanks a lot for the testing, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
