Next strange headers are installed to my system with git version of qt: btree.h crc32.h debian_qsql_odbc.h deflate.h ftglue.h ftxgdef.h ftxgpos.h ftxgsub.h ftxopenf.h ftxopen.h hash.h inffast.h inffixed.h inflate.h inftrees.h jri.h jri_md.h jritypes.h moc_yacc.h npapi.h npupp.h opcodes.h os.h otlbuffer.h pager.h parse.h pngasmrd.h pngconf.h
Also all private headers are installed to include dir as well as to include/private.
This is a BUG? Or they are used by something?
At least hash.h breaks compilation of kopete with jabber protocol.
My configuration string: ./configure -sm -thread -stl -system-libjpeg -verbose -largefile -qt-imgfmt-jpeg -qt-imgfmt-mng -qt-imgfmt-png -tablet -system-libmng -system-libpng -xft -platform linux-g++ -xplatform linux-g++ -xrender -prefix /usr/qt/3 -libdir /usr/qt/3/lib64 -fast -no-sql-odbc -L/usr/lib64 -no-nis -no-sql-mysql -no-sql-psql -no-sql-ibase -no-sql-sqlite -no-cups -disable-opengl -release -no-g++-exceptions -no-xinerama -system-zlib -qt-gif -ipv6 -dlopen-opengl
Next strange headers are installed to my system with git version of qt: btree.h crc32.h debian_qsql_odbc.h deflate.h ftglue.h ftxgdef.h ftxgpos.h ftxgsub.h ftxopenf.h ftxopen.h hash.h inffast.h inffixed.h inflate.h inftrees.h jri.h jri_md.h jritypes.h moc_yacc.h npapi.h npupp.h opcodes.h os.h otlbuffer.h pager.h parse.h pngasmrd.h pngconf.h
Also all private headers are installed to include dir as well as to include/private.
This is a BUG? Or they are used by something?
At least hash.h breaks compilation of kopete with jabber protocol.
My configuration string: ./configure -sm -thread -stl -system-libjpeg -verbose -largefile -qt-imgfmt-jpeg -qt-imgfmt-mng -qt-imgfmt-png -tablet -system-libmng -system-libpng -xft -platform linux-g++ -xplatform linux-g++ -xrender -prefix /usr/qt/3 -libdir /usr/qt/3/lib64 -fast -no-sql-odbc -L/usr/lib64 -no-nis -no-sql-mysql -no-sql-psql -no-sql-ibase -no-sql-sqlite -no-cups -disable-opengl -release -no-g++-exceptions -no-xinerama -system-zlib -qt-gif -ipv6 -dlopen-opengl
Looks to me that these header files were part of the original qt3 but were only in a directory called 3rdparty. With Trinity they all still exist in the same 3rdparty directory but are now sym linked to the copy in the 3rdparty directory. Looks like those sym links have existed in Trinity since the initial import.
Tim will have answer that question.
There are some open bug tracker items against kopete jabber. Regarding your specific error, there is a hash.h in the tdenetwork sources:
tdenetwork/kopete/protocols/jabber/libiris/iris/xmpp-core/hash.h
Perhaps test a patch by changing all occurrences of #include "hash.h" to #include "xmpp-core/hash.h"?
Darrell
2012/11/21 Darrell Anderson humanreadable@yahoo.com:
Looks to me that these header files were part of the original qt3 but were only in a directory called 3rdparty. With Trinity they all still exist in the same 3rdparty directory but are now sym linked to the copy in the 3rdparty directory. Looks like those sym links have existed in Trinity since the initial import.
Tim will have answer that question.
There are some open bug tracker items against kopete jabber. Regarding your specific error, there is a hash.h in the tdenetwork sources:
tdenetwork/kopete/protocols/jabber/libiris/iris/xmpp-core/hash.h
Perhaps test a patch by changing all occurrences of #include "hash.h" to #include "xmpp-core/hash.h"?
Darrell
Changing the include in kopete/jabber is just a workaround not a solution. IMHO symlinks to those headers should be just removed from qt3/include dir (rm include/{[q^]*.h,*_p.h})... it seems works well for me: tqtinterface and kdelibs compiles ok.
Changing the include in kopete/jabber is just a workaround not a solution. IMHO symlinks to those headers should be just removed from qt3/include dir (rm include/{[q^]*.h,*_p.h})... it seems works well for me: tqtinterface and kdelibs compiles ok.
In the original qt 3.3.8b sources ther are many sym links. Comparing those sources to Trinity indicates that probably only those sym links to src/3rdparty/*/*.h should be broken.
If Tim doesn't pipe in soon on this conversation then file a Build issue bug report with a status of Blocker.
Darrell