Serghei,
Continuing the build in the 'pristine' environment, I ran into the following
kdebase issue:
[ 16%] Building CXX object
kcontrol/style/CMakeFiles/kcm_style-module.dir/stylepreview.cpp.o
cd /build/src/build/kcontrol/style && /usr/bin/c++ -Dkcm_style_module_EXPORTS
-DHAVE_CONFIG_H -march=x86-64 -mtune=generic -O2 -pipe -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC
-I/build/src/build/kcontrol/style -I/build/src/build -I/opt/trinity/include
-I/opt/qt/include -I/opt/qt/include/tqt -o
CMakeFiles/kcm_style-module.dir/stylepreview.cpp.o -c
/build/src/build/kcontrol/style/stylepreview.cpp
In file included from /build/src/build/kcontrol/style/stylepreview.cpp:30:0:
/build/src/build/kcontrol/style/stylepreview.ui.h: In member function 'virtual
void StylePreview::init()':
/build/src/build/kcontrol/style/stylepreview.ui.h:36:32: error:
'QWIDGET_OBJECT_NAME_STRING' was not declared in this scope
/build/src/build/kcontrol/style/stylepreview.ui.h:43:41: error: 'Q_NoFocus' was
not declared in this scope
make[2]: *** [kcontrol/style/CMakeFiles/kcm_style-module.dir/stylepreview.cpp.o]
Error 1
make[2]: Leaving directory `/build/src/build'
make[1]: *** [kcontrol/style/CMakeFiles/kcm_style-module.dir/all] Error 2
make[1]: Leaving directory `/build/src/build'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Is this a build error on my end, or is this a CMake or header issue?
--
David C. Rankin, J.D.,P.E.
Hi guys!
working i refresh all the available patches of qt3 and qt3 trinity
patches... now there's no "hunks"..
BUT: i need info about it! theres some patches that repeat! and
re-defines a coupe of functions! i filter some one but i wnat to fix
all existences of issues and fixeds from any project, currently i have
the trinity patches, ARCH patches, Debian patches, some from WinBuntu
and i not found SUSE and if there any others please send me please!
i any found the info about every/any patch please report but with link
info.. merge unkown patches its not segure!
inside patche stheres info (only some) about fixed, but no links
povided, and qt nokia bug traker not have history on qt3 complete
fixeds o open bugs!
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
Serghei,
After building qt3 in a pristine build environment, I thought I would build
the rest of trinity there while I had the chance. So far, the dependencies have
built without issue:
trinity-qt3-3.3.8c-1-x86_64.pkg.tar.xz
trinity-pyqt3-3.18.1-9-x86_64.pkg.tar.xz
(poppler-qt3 still fails)
trinity-dbus-1-qt3-0.9-7.2-x86_64.pkg.tar.xz
trinity-tqtinterface-1230411-1-x86_64.pkg.tar.xz
Building arts, I have run into another .moc file that isn't generated. This
time it is qiomanager_p.moc. The build gets to 100% and then dies with:
[100%] Building CXX object qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o
cd /build/src/build/qtmcop && /usr/bin/c++ -Dqtmcop_shared_EXPORTS
-DHAVE_CONFIG_H -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-march=x86-64 -mtune=generic -O2 -pipe -fPIC -I/opt/qt/include
-I/opt/qt/include/tqt -I/build/src/build/qtmcop -I/build/src/build/mcop
-I/build/src/arts/mcop -include tqt.h -o
CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o -c /build/src/arts/qtmcop/qiomanager.cc
/build/src/arts/qtmcop/qiomanager.cc:299:28: fatal error: qiomanager_p.moc: No
such file or directory
compilation terminated.
make[2]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o] Error 1
make[2]: Leaving directory `/build/src/build'
make[1]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/all] Error 2
make[1]: Leaving directory `/build/src/build'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Checking the build directory -- no qiomanager_p.moc was every generated.
Could you take a look and see if this is like the kdevelop issue :)
--
David C. Rankin, J.D.,P.E.
All,
In response to a lot of the traffic on this mailing list, and in order to
prevent fragmentation of Qt3 versions via distro-specific patches, I have
added Qt3 3.3.8c into the Trinity SVN here:
http://svn.trinitydesktop.org/websvn/listing.php?repname=Trinity&path=%2Fma…
It can be checked out into the current working directory with a command
similar to this (if you do not have an SVN account simply remove the
--username=<username> portion of the command):
svn co http://svn.trinitydesktop.org/svn/trinity/dependencies/qt3 .
--username=<username>
The version currently in SVN has had the version number bumped to 3.3.8d,
and includes many of the Qt3 bugfix and security patches commonly in use
today. This version is ready to accept new bugfixes, such as a repair for
the gcc 4.6 header #include issue currently being discussed on this list.
If you want the ability to commit to this Qt3 branch in SVN please write
me directly at kb9vqf(a)pearsoncomputing.net and request an SVN account. If
you already have an SVN account at svn.trinitydesktop.org but cannot
commit to this branch, please include your username so that I can grant
write access to your account.
I hope this decision will aid all involved in keeping Qt3 running smoothly
and compiling on new platforms!
Timothy Pearson
Trinity Desktop Project
I apologize if you get 2 copies of this message, I never saw it come through to
the list....
-------- Original Message --------
Serghei,
After building qt3 in a pristine build environment, I thought I would build
the rest of trinity there while I had the chance. So far, the dependencies have
built without issue:
trinity-qt3-3.3.8c-1-x86_64.pkg.tar.xz
trinity-pyqt3-3.18.1-9-x86_64.pkg.tar.xz
(poppler-qt3 still fails)
trinity-dbus-1-qt3-0.9-7.2-x86_64.pkg.tar.xz
trinity-tqtinterface-1230411-1-x86_64.pkg.tar.xz
Building arts, I have run into another .moc file that isn't generated. This
time it is qiomanager_p.moc. The build gets to 100% and then dies with:
[100%] Building CXX object qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o
cd /build/src/build/qtmcop && /usr/bin/c++ -Dqtmcop_shared_EXPORTS
-DHAVE_CONFIG_H -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL
-DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT
-march=x86-64 -mtune=generic -O2 -pipe -fPIC -I/opt/qt/include
-I/opt/qt/include/tqt -I/build/src/build/qtmcop -I/build/src/build/mcop
-I/build/src/arts/mcop -include tqt.h -o
CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o -c /build/src/arts/qtmcop/qiomanager.cc
/build/src/arts/qtmcop/qiomanager.cc:299:28: fatal error: qiomanager_p.moc: No
such file or directory
compilation terminated.
make[2]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/qiomanager.cc.o] Error 1
make[2]: Leaving directory `/build/src/build'
make[1]: *** [qtmcop/CMakeFiles/qtmcop-shared.dir/all] Error 2
make[1]: Leaving directory `/build/src/build'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Checking the build directory -- no qiomanager_p.moc was every generated.
Could you take a look and see if this is like the kdevelop issue :)
--
David C. Rankin, J.D.,P.E.
--
David C. Rankin, J.D.,P.E.
All, (Baho and Calvin especially)
I need to get poppler-qt3 building to enable -DWITH_PDF=ON in kdegraphics.
Right now I have kdegraphics on Arch building with:
cmake ${srcdir}/${_svnmod} \
-DCMAKE_INSTALL_PREFIX=${trinity_prefix} \
-DCMAKE_VERBOSE_MAKEFILE=ON \
-DQT_VERSION=3 \
-DCMAKE_CXX_FLAGS="-fpermissive" \
-DWITH_T1LIB=ON \
-DWITH_LIBPAPER=ON \
-DWITH_TIFF=ON \
-DWITH_OPENEXR=ON \
-DWITH_PAM=ON \
-DBUILD_ALL=ON
make
# -DWITH_PDF=ON \ (waiting on poppler-qt3)
poppler-qt3 was building a month or so ago, but now I'm stuck. The regular
arch version built up until the gcc 4.6 change (or just a little before). Now on
the regular Arch install it fails with the following error:
make[2]: Entering directory
`/home/david/arch/pkg/bld/poppler-qt3/src/poppler-0.16.4/qt'
CXX poppler-document.lo
In file included from /opt/qt/include/qstringlist.h:45:0,
from /opt/qt/include/qcolor.h:46,
from /opt/qt/include/qpixmap.h:46,
from ./poppler-qt.h:33,
from poppler-document.cc:23:
/opt/qt/include/qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a type
/opt/qt/include/qvaluelist.h:167:13: error: 'ptrdiff_t' does not name a type
In file included from /opt/qt/include/qstringlist.h:45:0,
from /opt/qt/include/qcolor.h:46,
from /opt/qt/include/qpixmap.h:46,
from ./poppler-qt.h:33,
from poppler-document.cc:23:
/opt/qt/include/qvaluelist.h:427:13: error: 'ptrdiff_t' does not name a type
make[2]: *** [poppler-document.lo] Error 1
make[2]: Leaving directory
`/home/david/arch/pkg/bld/poppler-qt3/src/poppler-0.16.4/qt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/david/arch/pkg/bld/poppler-qt3/src/poppler-0.16.4'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
With the trinity-poppler-qt3, I had to add an export adding
/opt/qt/lib/pkgconfig to the PKGBUILD:
export PKG_CONFIG_PATH=/opt/qt/lib/pkgconfig:${PKG_CONFIG_PATH}
then the build gets past the configure error of:
"configure: error: Qt development libraries not found"
the fatal error now is:
make[2]: Entering directory
`/home/david/tblds/trinity-poppler-qt3/src/poppler-0.16.4/qt'
CXX poppler-document.lo
CXX poppler-fontinfo.lo
CXX poppler-link.lo
CXX poppler-page.lo
In file included from poppler-page.cc:28:0:
/opt/qt/include/qimage.h: In member function 'bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const':
/opt/qt/include/qimage.h:61:61: warning: suggest parentheses around '&&' within
'||' [-Wparentheses]
poppler-page.cc: In member function 'QImage Poppler::Page::renderToImage(double,
double, bool) const':
poppler-page.cc:76:18: warning: variable 'color_ptr' set but not used
[-Wunused-but-set-variable]
CXX poppler-page-transition.lo
CXX poppler-private.lo
CXXLD libpoppler-qt.la
/usr/bin/ld: cannot find -lqt-mt
collect2: ld returned 1 exit status
make[2]: *** [libpoppler-qt.la] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-poppler-qt3/src/poppler-0.16.4/qt'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/david/tblds/trinity-poppler-qt3/src/poppler-0.16.4'
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I don't understand how there is a ld error on -lqt-mt -- it's there:
18:27 trinity:~/tblds/trinity-poppler-qt3> l /opt/qt/lib/
<snip>
-rw-r--r-- 1 root root 809 May 5 16:01 libqt-mt.prl
lrwxrwxrwx 1 root root 17 May 5 16:00 libqt-mt.so -> libqt-mt.so.3.3.8
lrwxrwxrwx 1 root root 17 May 5 16:00 libqt-mt.so.3 -> libqt-mt.so.3.3.8
lrwxrwxrwx 1 root root 17 May 5 16:00 libqt-mt.so.3.3 -> libqt-mt.so.3.3.8
-rwxr-xr-x 1 root root 8407876 May 5 16:01 libqt-mt.so.3.3.8
<snip>
I need help sorting both out. Anybody see anything that sticks out above?
--
David C. Rankin, J.D.,P.E.
Hi all,
May Meeting will probably be postponed due to us frozen on cmake.
If anyone still has a topic they *really* need to discuss, or if
anyone wants to help speed up porting,
throw us a message at irc.freenode.net/#trinity-desktop.
PS. If anyone hasn't seen, there's a new trinity website (trinitydesktop.org).
PSS. gcc46 problems are being corrected. For those of you who want to give
Trinity a try at building, make sure you know what gcc version you are using.
AFAIK, Fedora 15+, openSUSE Factory, Arch Linux, and Debian are on this version.
--
later, Robert Xu
Tim, Serghei,
As we find the headers that need to be patched with '#include <cstddef>', can
those be updated in SVN? Is there any reason not? If adding the include won't
impact those building on gcc < 4.6, then I say we do it so that the code is 4.6
compliant and won't need fixing later.
What say the experts?
So far I have:
kdegraphics:
--- kdegraphics/kviewshell/plugins/djvu/libdjvu/GSmartPointer.h
+++ kdegraphics/kviewshell/plugins/djvu/libdjvu/GSmartPointer.h 2011-05-08
11:47:20.000000000 -0500
@@ -56,6 +56,7 @@
#ifndef _GSMARTPOINTER_H_
#define _GSMARTPOINTER_H_
+#include <cstddef>
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
They can be handled in the build scripts, but I would like to minimize the
proliferation of patch files and eliminated the if "already applied" then "don't
patch again dummy" fi statements :p
--
David C. Rankin, J.D.,P.E.