trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: August 2014

KOffice workaround for raspbian-wheezy

From: Slávek Banko <slavek.banko@...>
Date: Wed, 27 Aug 2014 02:31:16 +0200
Hi all,

from the very beginning, when they were included builds for raspbian-wheezy, I
watching FTBFS in KOffice with reference to a compiler bug. See:

/build/buildd/koffice-trinity-14.0.0-r313/./chalk/core/kis_exif_value.cc: In member function 'TQString ExifValue::toString(uint)':
/build/buildd/koffice-trinity-14.0.0-r313/./chalk/core/kis_exif_value.cc:685:1: error: unrecognizable insn:
(insn 676 675 677 19 (set (subreg:SI (reg:DI 378 [ D.20205_111->m_sbyte ]) 0)
        (sign_extend:SI (mem/s:QI (plus:SI (mult:SI (reg/v:SI 269 [ i ])
                        (const_int 8 [0x8]))
                    (reg/f:SI 374 [ this_1(D)->m_value ])) [0 D.20205_111->m_sbyte+0 S1 A64]))) /usr/share/tqt3/include/ntqstring.h:949 -1
     (nil))
/build/buildd/koffice-trinity-14.0.0-r313/./chalk/core/kis_exif_value.cc:685:1: internal compiler error: in extract_insn, at recog.c:2109
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.6/README.Bugs> for instructions.


Because in the last days Michele worked on fix build KOffice with Ruby 2.1 and
libwpd-0.10 (good work Michele!), I devoted some time to explore the problem
on Raspbian. I've isolated the problem and then created a workaround. Please
see the attached patch.

What is your opinion?
Can I push it?

Thanks,
-- 
Sl�vek

Attachments: