It seems that libexiv2-10 is not compatible with KDE3. After update of
libexiv2 from libexiv2-9 to libexiv2-10 in openSUSE:Factory all KDE3 packages
that require libexiv2 became broken.
Any thoughts of how to mitigate this?
Hi all,
Please note that the new NetworkManager release changes the API in a
way that breaks many applications using it.
The Trinity NetworkManager applet should be increased in priority for
cmake so that changes may be made to accommodate this breakage.
--
later, Robert Xu
Tim,
I apologize for the delays, life seems to have caught up with me recently. This week and the following are finals for the semester so I am under a great stress and large workload. I also have not been able to successfully install Trinity either on Arch Linux. Baho and David haven't grasped the concept of portability so I don't have it working.
Again Sorry,
Calvin Morrison.
Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
>Hi Serghei, Calvin,
>
>Can you two please update me on the CMake status of kdegraphics? I would
>like to keep things moving if possible; I know Calvin has on the Etherpad
>that he is waiting for some kind of macro from Serghei; if this could be
>coordinated and fixed I would appreciate it.
>
>Once kdegraphics is complete I will initate TQt4 conversion and autobuilds
>on this end.
>
>Thanks!
>
>Tim
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
>For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
>Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
>Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
What is the best way to troubleshoot run-time crashes?
Do the packages have to be built a certain way?
I've read about backtraces, core dumps, and using gdb. I'm no programmer, so what is the best way for me to troublesoot?
In particular, I am running KDE 3.5.10, recompiled for Slackware 13.1. KMail always now crashes whenever I try to do anything with the composer window (save as draft, send, etc.). Boom. Just disappears. Almost as if I had started KMail with the --compose option. The app disappears and I have to restart KMail. The funny thing is the message gets stored in the Outbox.
I want to troubleshoot in case this bug carries over to Trinity.
Thanks.
Darrell
Tim,
Here are a bunch of patches I don't think have been merged into Trinity.
http://humanreadable.nfshost.com/trinity/patches/
I checked them against svn (my head hurts!). I might have missed a few because of the changes to run through tqtinterface, but not many if I did.
Some of them will need to be converted to using TQT.
I found these patches while building KDE 3.5.10 on Slackware 13.1. There were many more patches, but those I did not post have been merged into Trinity.
There are quite a few patches against qt3. Several apps include patches for libpng 1.4.
Darrell
Guys,
I have finally gotten a few minutes to dive back into Trinity. To my chagrin,
we have Arch has bumped from gcc 4.5 to gcc 4.6. I am having problems building
Qt3. Adding to the difficulty, the Qt3 build script for Arch has been through a
number of changes lately and I haven't had time to verify the new build script
under gcc 4.5 before the jump to gcc 4.6. So I am working to understand whether
this build failure is gcc related or if it is a normal screw-up on my end.
The build is failing in the middle of the build, so this leads me to think
this might be gcc related. If anybody can look at the error and determine
whether this is a gcc issue or not, I would greatly appreciate it. I think what
I'll do is drop back to a build script that I know was working on gcc 4.5 and
confirm, but in the interim, I thought I would post the error in hope somebody
else had seen this already. What does this error look like to the masters?:
g++ -c -pipe -Wall -W -march=i686 -mtune=generic -O2 -pipe -D_REENTRANT -fPIC
-DQT_SHARED -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT
-D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_IMAGEIO_MNG
-DQT_NO_IMAGEIO_JPEG -DQT_NO_IMAGEIO_PNG -DQT_BUILTIN_GIF_READER=1
-DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE
-DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC
-I/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/mkspecs/linux-g++ -I.
-I/usr/include/freetype2 -I3rdparty/opentype -I../include -I/usr/X11R6/include
-I/usr/X11R6/include -I.moc/release-shared-mt/ -o
.obj/release-shared-mt/qapplication_x11.o kernel/qapplication_x11.cpp
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:91:13: error: ‘ptrdiff_t’ does not name a type
../include/qvaluelist.h:167:13: error: ‘ptrdiff_t’ does not name a type
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:427:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:110:13: error: ‘ptrdiff_t’ does not name a type
../include/qmap.h:226:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:607:13: error: ‘ptrdiff_t’ does not name a type
kernel/qapplication_x11.cpp: In member function ‘int
QApplication::x11ProcessEvent(XEvent*)’:
kernel/qapplication_x11.cpp:3693:54: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:3706:54: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateMouseEvent(const XEvent*)’:
kernel/qapplication_x11.cpp:4122:30: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateKeyEventInternal(const XEvent*, int&, QString&, int&, char&,
int&, QEvent::Type&, bool)’:
kernel/qapplication_x11.cpp:5161:8: warning: suggest explicit braces to avoid
ambiguous ‘else’ [-Wparentheses]
kernel/qapplication_x11.cpp:5232:52: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:5235:52: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In function ‘int isPaintOrScrollDoneEvent(Display*,
XEvent*, XPointer)’:
kernel/qapplication_x11.cpp:5524:34: warning: suggest parentheses around ‘&&’
within ‘||’ [-Wparentheses]
make[2]: *** [.obj/release-shared-mt/qapplication_x11.o] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/src'
make[1]: *** [sub-src] Error 2
make[1]: Leaving directory `/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b'
make: *** [init] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I'll go try an older build script that used qt-x11-free-3.3.8 instead of
qt-x11-free-3.3.8b. I'll report back :p
--
David C. Rankin, J.D.,P.E.
On Apr 30, 2011, at 17:57, "David C. Rankin" <drankinatty(a)suddenlinkmail.com>
wrote:
Guys,
I have finally gotten a few minutes to dive back into Trinity. To my
chagrin,
we have Arch has bumped from gcc 4.5 to gcc 4.6. I am having problems
building
Qt3. Adding to the difficulty, the Qt3 build script for Arch has been
through a
number of changes lately and I haven't had time to verify the new build
script
under gcc 4.5 before the jump to gcc 4.6. So I am working to understand
whether
this build failure is gcc related or if it is a normal screw-up on my end.
The build is failing in the middle of the build, so this leads me to think
this might be gcc related. If anybody can look at the error and determine
whether this is a gcc issue or not, I would greatly appreciate it. I think
what
I'll do is drop back to a build script that I know was working on gcc 4.5
and
confirm, but in the interim, I thought I would post the error in hope
somebody
else had seen this already. What does this error look like to the masters?:
g++ -c -pipe -Wall -W -march=i686 -mtune=generic -O2 -pipe -D_REENTRANT
-fPIC
-DQT_SHARED -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT
-D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITSd -DQT_NO_IMAGEIO_MNG
-DQT_NO_IMAGEIO_JPEG -DQT_NO_IMAGEIO_PNG -DQT_BUILTIN_GIF_READER=1
-DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE
-DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC
-I/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/mkspecs/linux-g++ -I.
-I/usr/include/freetype2 -I3rdparty/opentype -I../include
-I/usr/X11R6/include
-I/usr/X11R6/include -I.moc/release-shared-mt/ -o
.obj/release-shared-mt/qapplication_x11.o kernel/qapplication_x11.cpp
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:91:13: error: ‘ptrdiff_t’ does not name a type
../include/qvaluelist.h:167:13: error: ‘ptrdiff_t’ does not name a type
In file included from ../include/qmap.h:49:0,
from kernel/qmime.h:46,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qvaluelist.h:427:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:110:13: error: ‘ptrdiff_t’ does not name a type
../include/qmap.h:226:13: error: ‘ptrdiff_t’ does not name a type
In file included from kernel/qmime.h:46:0,
from kernel/qevent.h:48,
from kernel/qobject.h:48,
from kernel/qwidget.h:46,
from kernel/qdesktopwidget.h:43,
from kernel/qapplication.h:45,
from kernel/qapplication_x11.cpp:67:
../include/qmap.h:607:13: error: ‘ptrdiff_t’ does not name a type
kernel/qapplication_x11.cpp: In member function ‘int
QApplication::x11ProcessEvent(XEvent*)’:
kernel/qapplication_x11.cpp:3693:54: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:3706:54: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateMouseEvent(const XEvent*)’:
kernel/qapplication_x11.cpp:4122:30: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In member function ‘bool
QETWidget::translateKeyEventInternal(const XEvent*, int&, QString&, int&,
char&,
int&, QEvent::Type&, bool)’:
kernel/qapplication_x11.cpp:5161:8: warning: suggest explicit braces to
avoid
ambiguous ‘else’ [-Wparentheses]
kernel/qapplication_x11.cpp:5232:52: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp:5235:52: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
kernel/qapplication_x11.cpp: In function ‘int
isPaintOrScrollDoneEvent(Display*,
XEvent*, XPointer)’:
kernel/qapplication_x11.cpp:5524:34: warning: suggest parentheses around
‘&&’
within ‘||’ [-Wparentheses]
make[2]: *** [.obj/release-shared-mt/qapplication_x11.o] Error 1
make[2]: Leaving directory
`/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b/src'
make[1]: *** [sub-src] Error 2
make[1]: Leaving directory
`/home/david/tblds/trinity-qt3/src/qt-x11-free-3.3.8b'
make: *** [init] Error 2
==> ERROR: A failure occurred in build().
Aborting...
I'll go try an older build script that used qt-x11-free-3.3.8 instead of
qt-x11-free-3.3.8b. I'll report back :p
There should be a patch at openSUSE for gcc46
Hi Serghei, Calvin,
Can you two please update me on the CMake status of kdegraphics? I would
like to keep things moving if possible; I know Calvin has on the Etherpad
that he is waiting for some kind of macro from Serghei; if this could be
coordinated and fixed I would appreciate it.
Once kdegraphics is complete I will initate TQt4 conversion and autobuilds
on this end.
Thanks!
Tim
