On 8 November 2011 17:42, Steve McIntyre
On Tue, Nov 08, 2011 at 04:10:30PM +0100, Joop Boonen wrote:
On Tue, November 8, 2011 3:18 pm, Steve McIntyre wrote:
Please do *not* do stick with "arm-linux-gnueabi" if you're doing hard-float. It *will* cause you pain in the future if you ever care about cross-distro binary compatibility. The change in the ABI name is deliberate, and is there for a reason. If you have toolchain problems with it, please share them and you'll probably get help.
Steve, does this mean that if we would use the videodrivers taken from the Efika MX ARMHF image on page http://www.powerdeveloper.org/platforms/efikamx/linux ? That this wouldn't work because of arm-linux-gnueabi in stead of arm-linux-gnueabihf?
Potentially, yes. Konstantinos is the guy at Genesi working on those, so I'll let him respond - he'll know for sure. Added to CC above... :-)
Hi, well, mixing binaries built with different triplets is going to be tricky, it may work, as the ABI is the same, but I cannot guarantee you will have ABI stability or that they will run at all, esp with the dynamic linker expecting libs in /usr/lib/arm-linux-gnueabihf. I would still advise getting the same triplet as the rest of us have agreed upon (Debian, Ubuntu, Fedora). Fedora in fact will use -marm instead of -mthumb to minimise the build-failures (and they are a lot!). However, in the Debian BTS there is a big number of patches for armhf which you might find useful. Also have in mind I found and filed ~8 gcc ICE bug reports for armhf, which you may or may not have to tackle with yourselves in the future, regardless of the triplet. In short, one triplet to rule them all, one triplet to bind them, etc, etc. :) Regards Konstantinos -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org