Am Dienstag, 8. November 2011, 16:12:10 schrieb Alexander Graf:
On 11/08/2011 03:18 PM, Steve McIntyre wrote:
On Tue, Nov 08, 2011 at 03:23:46PM +0100, Alexander Graf wrote:
On 11/08/2011 02:31 PM, Peter Czanik wrote:
my questions relate to it:
- what triplet is used to compile hardfloat binaries? In the archives I found: "Currently we're building with -march=armv7-a -mfloat-abi=hard -mfpu=vfp3-d16 -mthumb." Is it still the case? (I was asked by Debian ARM HF project lead last week...)
Yes, we're using the common ground here. However, our triplet is "gnueabi" instead of "gnueabihf" at the last position because a lot of parts in our toolchain break with gnueabihf and we haven't found a good reason to not use it.
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.
I'm not sure what exactly you're referring to. IIRC RPM (at least last time we checked) ignored the gnueabi flag for the comparison. I haven't really dug into the problem myself too much though.
Adrian and Dirk, do you remember what exactly the problems were we were facing?
I know there were a few checks explicit checking for gnueabi, but others did check for gnueabi*. However, only very few packages should be affected, so it would not be a problem to switch. Since do anyway build for "suse-linux-$arch" without the -gnu by default we would just need to change the affected packages. (we strip the -gnu also on other architectures which is not a arm decision but a generic SUSE one.)
Alex
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org