Found on all gsf versions since 1.14.9-1:
-snip-
creating gsf-scan
gtk-doc: Running scanner gsf-scan
** ERROR **: Compilation trouble with endianess.
aborting...
sh: line 1: 7588 Aborted ( ./gsf-scan )
-snip-
Full build log:
Looking at the error in sources, it seems like floating point
issue. Armel (arm eabi) has natural floating point order.
--
To UNSUBSCRIBE, email to debian-bugs...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
On Thu, Oct 23, 2008 at 00:05:04 +0300, Riku Voipio wrote:
> Found on all gsf versions since 1.14.9-1:
>
> -snip-
> creating gsf-scan
> gtk-doc: Running scanner gsf-scan
>
> ** ERROR **: Compilation trouble with endianess.
gsf-scan is a generated file; the gtk-doc-tools package is responsible for
its template. Reassigning accordingly.
Ray
--
Would you rather be root or reboot?
> gsf-scan is a generated file; the gtk-doc-tools package is responsible for
> its template. Reassigning accordingly.
The error is coming from gsf-init. Reassigning accordingly.
gsf thinks only vfp enabled arm uses natural endian doubles. However,
eabi does that as well. As anyone using vfp is also using eabi,
the correct change is to switch the define.
I believe libgsf is actually broken on armel on older versions too,
it just that someone added runtime float detection to gsf-init that
exposes this br0kenness.
diff -ur old/libgsf-1.14.10/gsf/gsf-utils.c libgsf-1.14.10/gsf/gsf-utils.c
--- old/libgsf-1.14.10/gsf/gsf-utils.c 2008-07-01 12:56:53.000000000 +0000
+++ libgsf-1.14.10/gsf/gsf-utils.c 2008-10-23 07:03:25.000000000 +0000
@@ -73,7 +73,7 @@
* mixture.
*/
#define G_ARMFLOAT_ENDIAN 56781234
-#if defined(__arm__) && !defined(__vfp__) && (G_BYTE_ORDER == G_LITTLE_ENDIAN)
+#if defined(__arm__) && !defined(__ARM_EABI__) && (G_BYTE_ORDER == G_LITTLE_ENDIAN)
#define G_FLOAT_BYTE_ORDER G_ARMFLOAT_ENDIAN
#else
#define G_FLOAT_BYTE_ORDER G_BYTE_ORDER
--
"rm -rf" only sounds scary if you don't have backups
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
503144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems