The moment in which it segfaults is the first time it runs the
interpreter it has just built, "axi", during the build, so I guess the
whole interpreter is broken. I've tried a debugging build by hacking
debian/rules:
< ./cnf/bin/afnix-setup -o --prefix=/usr
> ./cnf/bin/afnix-setup -g --prefix=/usr # -o/-g turn each other
> off
and the cause of death is in exactly the same place, indeed the same
instruction (modulo code differences due to -O0 forced by the debug
build) - some callback to a constructor function whose address is
picked out of an array.
#0 0x4005064c in mksob () at Constant.cpp:29
#1 0x40258504 in get_serial_object (sid=33 '!') at Serial.cpp:63
#2 0x40258dc8 in afnix::Serial::getserial (sid=33 '!') at Serial.cpp:163
#3 0x40258e48 in afnix::Serial::deserialize ([EMAIL PROTECTED]) at
Serial.cpp:171
(more of this output at n2100.martinwguy.co.uk/martin/arm/AFNIX)
HOWEVER
1.5.2-2 built fine on arm (but not armel - dunno if it was tried or not)
1.5.2-3.1 builds fine on armel but not arm - this should help narrow it down!
The changes are miniscule:
* Added gcc-4.3_support.dpatch to fix FTBFS with GCC 4.3 (Closes: #461964)
-> just removing -Werror from the gcc command line
* afnix-doc: should be Architecture:all (Closes: #451602)
-> This implies less work to do, so shouldn't break anything.
I've tried building without -B (for superstition), and it dies at
the same command, with a Bus Error this time instead of SEGV (I have
the box set to signal misaligned accesses instead of returning garbled
values)
* Fixed FTBFS: dpkg-shlibdeps: failure: couldn't find library libafnix-
eng.so.1.5 needed by debian/afnix/usr/lib/afnix/libafnix-
net.so.1.5.2. (Closes: #453794)
-> it doesn't get this far.
Given that it builds on every other arch, including armel, and since
1.5.2-2 was built 15-Jul-2007 on arm with gcc-4.2 or 4.1, the most
likely cause seems that it is either tickling a bug in gcc-4.3 for ARM
old-ABI, or that gcc-4.3 on ARM-OABI is violating some assumption
afnix has about it.
Yeah, the easy answer is to drop the package from Lenny, but it's annoying.
I've mailed one of the authors asking if they want to look at it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
