Bug#342545: qt-x11-free FTBFS
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 5 lines
That would be wonderful if you, or another hppa porter, could track down where the bug lies. libgcc2 is almost certainly the wrong package, since nothing should be *using* libgcc2 in a fresh build of qt-x11-free; it may be a bug in libgcc4 instead, but I think that's yet to be determined. In the meantime, I think it's best to reassign this back to qt-x11-free.
This might be a nan bug. There is one GCC nan fix that's only installed on the trunk:
2006-05-24 John David Anglin <[email protected]>
PR target/27627
* pa/pa-modes.def: Use mips_single_format, mips_double_format and mips_quad_format formats instead of ieee_single_format, ieee_double_format and ieee_quad_format formats, respectively.
However, I think the real bug is here:
Quoted 2 lines
Quoted 2 lines
0x40cb2150in negNan () attools/qlocale.cpp:131
131 *((const double *)le_neg_nan_bytes));
PA-RISC requires strict alignment and it's highly likely that the pointer le_neg_nan_bytes isn't aligned to an eight byte boundary. You could see the faulting insn by disassembling around 0x40cb2150 to be sure. The nan problem fixed by the above change would cause a SIGFPE instead of a SIGBUS.
I'm fairly certain we have a bug in handling unaligned fixups for doubles in the kernel. This caused a problem for libffi. This depends on whether the kernel is 32/64 bits.
As Kyle pointed out, unaligned fixups by the kernel are expensive and they should be avoided. tools/qlocale.cpp appears to be a qt-x11-free routine, so I agree that the reassignment was correct.
Dave
Signature · 7 lines
J. David Anglin [email protected] National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]