kipi-plugins-kde4 and digikam-kde4 picks up qt3 headers from qt-copy-3.3.8_9

Matt datahead4 at gmail.com
Wed Feb 18 12:34:14 PST 2009


On Wed, Feb 18, 2009 at 2:22 PM, Goran Lowkrantz <glz at hidden-powers.com> wrote:
> --On Wednesday, February 18, 2009 2:13 PM -0600 Matt <datahead4 at gmail.com>
> wrote:
>
>> On Wed, Feb 18, 2009 at 12:58 PM, Goran Lowkrantz <glz at hidden-powers.com>
>> wrote:
>>>
>>> Trying to build the KDE4 versions of these ports fails as the build pick
>>> up old headers from qt3 through qt-copy-3.3.8_9.
>>>
>>>
>>> [  0%] Building CXX object
>>> common/libkipiplugins/CMakeFiles/kipiplugins.dir/kpaboutdata.o
>>> In file included from
>>> /var/ports/usr/ports/graphics/kipi-plugins-kde4/work/kipi-plugins-0.2.0-
>>> beta6/common/libkipiplugins/kpaboutdata.cpp:23:
>>> /var/ports/usr/ports/graphics/kipi-plugins-kde4/work/kipi-plugins-0.2.0-
>>> beta6/common/libkipiplugins/kpaboutdata.h:42: error: expected ',' or
>>> '...' before '&' token
>>> /var/ports/usr/ports/graphics/kipi-plugins-kde4/work/kipi-plugins-0.2.0-
>>> beta6/common/libkipiplugins/kpaboutdata.h:46: error: ISO C++ forbids
>>> declaration of 'KLocalizedString' with no type
>>>
>>>
>>> /usr/local/include/qtextstream.h:298: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:301: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:304: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:307: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:308: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:309: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:310: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:311: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:312: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:313: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:314: error: expected initializer before
>>> '&' token
>>> /usr/local/include/qtextstream.h:316: error: expected initializer before
>>> 'qSetW'
>>> /usr/local/include/qtextstream.h:322: error: expected initializer before
>>> 'qSetFill'
>>> /usr/local/include/qtextstream.h:328: error: expected initializer before
>>> 'qSetPrecision'
>>> In file included from /usr/local/include/qvaluelist.h:42,
>>>               from /usr/local/include/qtranslator.h:44,
>>>               from /usr/local/include/qapplication.h:45,
>>>               from
>>> /var/ports/usr/ports/graphics/digikam-kde4/work/digikam-0.10.0-rc2/libs/
>>> threadimageio/loadsavetask.cpp:29:
>>>
>>> # pkg_info -W /usr/local/include/qvaluelist.h
>>> /usr/local/include/qvaluelist.h was installed by package qt-copy-3.3.8_9
>>
>> After issuing "make configure" for the port, what value do you see in
>> the CMakeCache.txt file (located in ${WRKSRC} ) for the QT_INCLUDE_DIR
>> variable?
>>
>> What version of cmake do you have installed?  My version of cmake
>> 2.6.2 includes a block in the FindQt4.cmake file that reads:
>>
>>  # Set QT_QT_INCLUDE_DIR
>>  FIND_PATH(QT_QT_INCLUDE_DIR qglobal.h
>>    PATHS
>>    ${QT_INCLUDE_DIR}/Qt
>>    ${QT_LIBRARY_DIR}/QtCore.framework/Headers
>>    NO_DEFAULT_PATH
>>    )
>>
>> And if I'm reading that correctly, it shouldn't be looking for the
>> include headers in the base /usr/local/include directory at all.
>>
>> Matt
>
> # pkg_info -Ix cmake
> cmake-2.6.2         A cross-platform make
>
> QT_INCLUDE_DIR:PATH=/usr/local/include/qt4
>
> # ls /usr/local/include/qt4/
> Qsci            QtAssistant     QtDesigner      QtNetwork       QtSql
> QtUiTools       QtXmlPatterns
> Qt              QtCore          QtGui           QtOpenGL        QtSvg
> QtWebKit
> Qt3Support      QtDBus          QtHelp          QtScript        QtTest QtXml
>
> /glz

That looks like what I would expect to see.  I can't reproduce this
problem on my local machine, even with the qt33 port installed.

Sorry - I'm not sure what else to check.

Matt


More information about the freebsd-ports mailing list