On Thu, 12 Nov 2015 23:47:27 +0000 Wookey wookey@wookware.org wrote:
[]
But I'm not advocating it in any way, just trying to apply my previous experience with a 64-bit arch to a new one (my guess is that many "mere" folks would do that, so at least would be nice to have answers ready for them, that's why I cc: 96boards list).
Yes it's quite ingrained in x86-world but it really doesn't make much sense in arm world.
use <triplet>-gcc everywhere (x86 as well) and life will be good.
Works for me, thanks.
What are you actually trying to do anyway? I thought everyone had given up with ilp32, so we can ignore it? We have patches to make ilp32 behave like a proper ABI, but they are not yet upstreamed because there is no agreed syscall interface for the kernel + glibc to implement: https://wiki.linaro.org/Platform/arm64-ilp32
Well, I compiled an app, it eventually crashed, next logical step (based on x86_64 experience) is to build it in 32-bit mode, to see if it crashes again, or the crash is an artifact of 64-bitness.
Hmm, OK. You don't want ilp32. It's not finished or useful.
Just build for arm-linux-gnueabihf- .
Some info on crossbuilding on Debian/Ubuntu is here: https://wiki.debian.org/CrossCompiling but it's rather package-oriented. I could add some info on cross-building unpackaged-things if that would be helpful?
Yes, I may imagine that would be helpful. The page you link isn't one I'd look for, I even wonder if that's a thinko and you meant https://wiki.debian.org/CrossToolchains instead. Thanks for arm-linux-gnueabihf- suggestion, as I mentioned in the original email, I tried arm-linux-gnueabi- instead, that built, but didn't run. Unfortunately, few next weeks I don't have access to my Dragonboard, so testing that all will have to wait.
Wookey