Hi Mark, Mark H Weaver skribis: > Mark H Weaver writes: > >> Here's the declaration of QChar::byteOrderMark from qtools/qstring.h, >> included in the doxygen tarball: >> >> class Q_EXPORT Q_PACKED QChar { >> public: >> QChar(); >> QChar( char c ); >> QChar( uchar c ); >> QChar( uchar c, uchar r ); >> QChar( const QChar& c ); >> QChar( ushort rc ); >> QChar( short rc ); >> QChar( uint rc ); >> QChar( int rc ); >> >> QT_STATIC_CONST QChar null; // 0000 >> QT_STATIC_CONST QChar replacement; // FFFD >> QT_STATIC_CONST QChar byteOrderMark; // FEFF >> QT_STATIC_CONST QChar byteOrderSwapped; // FFFE >> QT_STATIC_CONST QChar nbsp; // 00A0 >> >> and here's its definition, from qtools/qstring.cpp line 12179: >> >> QT_STATIC_CONST_IMPL QChar QChar::byteOrderMark((ushort)0xfeff); >> >> Any suggestions? I've managed to avoid working with C++ so far in this >> millenium, so I'm a bit rusty. > > If some of these cases are difficult to work around, one option would be > to add a new 'gcc-final/fixed' package or similar, with this bug fixed, > and we could then add it as a 'native-input' to selected packages where > it's needed, e.g. doxygen on armhf. We could do that, though that means one more GCC to build, which isn’t great. If there are few ICEs, maybe we can just fix them individually. Ludo’.