Re: Bug#503144: FTBFS on armel: gsf-scan, ** ERROR **: Compilation trouble with endianess.
> > > -#if defined(__arm__) && !defined(__vfp__) && (G_BYTE_ORDER == G_LITTLE_ENDIAN)
> > > +#if defined(__arm__) && !defined(__ARM_EABI__) && (G_BYTE_ORDER == G_LITTLE_ENDIAN)
> libgsf was fixed a long time ago - before eabi stuff had any sort of
> plan in Debian. Using __vfp__ seemed like the best test at the time,
> as recommended to me by pb. I'm not sure when you end up with
> __ARM_EABI__ defined but __vfp__ not defined in practice, but I agree
> the change is now correct.
I dunno if the build script is setting __vfp__ somewhere.
Yes, unfortunately there is no direct test for old-ABI
middle-endianness as fas as I can see - you have to test for not
everthing else :-/
My best information is that if (__VFP_FP__ || __MAVERICK__) then we
store as pure IEEE little-endian, otherwise FPA format. (__VFP_FP__ is
also defined when EABI softfloat, because it reflects the FP format,
not VFP instructions necessarily) __MAVERICK__ semantically is also an
FP format, which happens to be the same. Yeah, it's all crazy.
M
Reply to: