[kde-freebsd] x11/kde4-baseapps fails to build under clang (a QT issue?)

[Raphael Kubo da Costa]

Chuck Burns <break19 at gmail.com> writes:

> In file included from
> /usr/ports/x11/kde4-baseapps/work/kde-baseapps-4.7.4/konq-plugins/domtreeviewer/domtreecommands.cpp:21: 
>
> In file included from
> /usr/ports/x11/kde4-baseapps/work/kde-baseapps-4.7.4/konq-plugins/domtreeviewer/domtreecommands.h:24:
> In file included from /usr/local/kde4/include/dom/dom_element.h:34:
> In file included from /usr/local/kde4/include/dom/css_value.h:30:
> In file included from /usr/local/kde4/include/dom/dom_string.h:26:
> In file included from /usr/local/kde4/include/kdebug.h:27:
> In file included from /usr/local/include/qt4/QtCore/QDebug:1:
> In file included from /usr/local/include/qt4/QtCore/qdebug.h:48:
> /usr/local/include/qt4/QtCore/qmap.h:107:17: error: invalid operands
> to binary expression ('const DOM::Node' and 'const DOM::Node')
>     return key1 < key2;
>            ~~~~ ^ ~~~~
> /usr/local/include/qt4/QtCore/qmap.h:782:49: note: in instantiation of
> function template specialization 'qMapLessThanKey<DOM::Node>'
> requested here
>         while ((next = cur->forward[i]) != e &&
> qMapLessThanKey<Key>(concrete(next)->key, akey))
>                                                 ^
> /usr/local/include/qt4/QtCore/qmap.h:562:28: note: in instantiation of
> member function 'QMap<DOM::Node, bool>::mutableFindNode' requested
> here 
>
>     QMapData::Node *node = mutableFindNode(update, akey);
>                            ^
> /usr/ports/x11/kde4-baseapps/work/kde-baseapps-4.7.4/konq-plugins/domtreeviewer/domtreecommands.cpp:137:17:
> note: in instantiation of member function 'QMap<DOM::Node,
> bool>::insert'
>       requested here
>   changedNodes->insert(node, true);
>                 ^

Finally fixed upstream in kde-baseapps (c3e23ca in the KDE/4.8 branch,
e5cdd82 in master). This was an interesting exercise in learning the
intricacies of C++, bored people can read the commit message for the
gory details ;)

I don't feel like adding the patch to the ports tree at the moment --
all these fixes I'm committing will be out with 4.8.0, so it can all be
fixed in a single shot (I don't know how many other build failures will
be uncovered in other modules).