------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-16 12:54 ------- Thanks, thanks, thanks Andreas to have fixed this problem. I will checkout source code and test. Just to remember : these files in kde bugzilla are certainly duplicates : http://bugs.kde.org/show_bug.cgi?id=133567 http://bugs.kde.org/show_bug.cgi?id=136086 http://bugs.kde.org/show_bug.cgi?id=132805 http://bugs.kde.org/show_bug.cgi?id=137204 http://bugs.kde.org/show_bug.cgi?id=135407 http://bugs.kde.org/show_bug.cgi?id=134999 http://bugs.kde.org/show_bug.cgi?id=131935 If your fix solve the problem these files will be closed... Witch will be the next Exiv2 release number ? Because i will update digiKam/kipi-plugins depencies before to release final. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-16 13:17 ------- Keeping my fingers crossed, but we need feedback first. The next version will be 0.12 -ahu. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from ahuggel@gmx.net
:(
exiv2 984, kipi-plugins 605460, digikam 605459 Crash when applying data on single image. There is no crash when walking through several selected images, but data isn't applied. Using host libthread_db library "/lib/tls/libthread_db.so.1". `shared object read from target memory' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1239930560 (LWP 13823)] [KCrash handler] #5 0xffffe410 in __kernel_vsyscall () #6 0xb61adef1 in raise () from /lib/tls/libc.so.6 #7 0xb61af83b in abort () from /lib/tls/libc.so.6 #8 0xb61e3ff5 in __fsetlocking () from /lib/tls/libc.so.6 #9 0xb61ea587 in malloc_usable_size () from /lib/tls/libc.so.6 #10 0xb61eaa02 in free () from /lib/tls/libc.so.6 #11 0xb63936f1 in operator delete () from /usr/lib/libstdc++.so.6 #12 0xb79a88ba in ~ValueType (this=0x1be50000) at /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ext/new_allocator.h:94 #13 0xb79ae3a3 in ~Exifdatum (this=0x86be288) at /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/memory:259 #14 0xb79b55bb in std::_Destroy<Exiv2::Exifdatum*, std::allocator<Exiv2::Exifdatum> > (__first=0x86be294, __last=0x86be54c, __alloc=@0xbfab53db) at /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ext/new_allocator.h:107 #15 0xb79ae692 in ~ExifData (this=0x869ea64) at /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_vector.h:273 #16 0xb79c8577 in ~JpegImage (this=0x869ea58) at jpgimage.hpp:123 #17 0xb4f1c8f1 in KIPIPlugins::Exiv2Iface::save () from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so #18 0xb4efa279 in KIPIMetadataEditPlugin::IPTCEditDialog::slotApply () from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so #19 0xb738ba8c in KDialogBase::qt_invoke () from /usr/local/kde/lib/libkdeui.so.4 #20 0xb4efa043 in KIPIMetadataEditPlugin::IPTCEditDialog::qt_invoke () from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so #21 0xb6a361bf in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0x0864fbb8 in ?? () #23 0xbfab5574 in ?? () #24 0x00000000 in ?? () _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From cmaessen casco demon nl 2006-11-17 01:05 ------- I'm sorry to say, but it looks even worse. As you asked I downloaded and compiled exiv2 svn rev. 984. Ran it with digiKam svn rev. 604964. Selected a few images, edited the caption-field, apply, crash. The same, but forward, crash. Tested on a single file, and the same results. Caspar. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From cmaessen casco demon nl 2006-11-17 01:10 ------- Forgot to mention that I lost all the EXIF-information of the first of the selected files, while it was the IPTC tags I was editing. Following is the backtrace of one of the crashes. Caspar. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1240709456 (LWP 2911)] [New Thread -1252365408 (LWP 2938)] [KCrash handler] #5 0xb787a453 in ~Exifdatum (this=0xb30d8ce4) at /usr/include/c++/4.1.0/memory:259 #6 0xb787d39b in ~ExifData (this=0xb3074704) at /usr/include/c++/4.1.0/bits/stl_construct.h:107 #7 0xb7896043 in ~JpegBase (this=0xb30746f8) at jpgimage.hpp:123 #8 0xb78961cd in ~JpegImage (this=0xb30746f8) at jpgimage.hpp:284 #9 0xb7e4eda3 in std::auto_ptr<Exiv2::Image>::~auto_ptr () from /opt/kde3/lib/libdigikam.so.0 #10 0xb38222d2 in KIPIPlugins::Exiv2Iface::save () from /opt/kde3/lib/kde3/kipiplugin_metadataedit.so #11 0xb37f2fcf in KIPIMetadataEditPlugin::IPTCEditDialog::slotApply () from /opt/kde3/lib/kde3/kipiplugin_metadataedit.so #12 0xb7260333 in KDialogBase::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #13 0xb37f5ab2 in KIPIMetadataEditPlugin::IPTCEditDialog::qt_invoke () from /opt/kde3/lib/kde3/kipiplugin_metadataedit.so #14 0xb68b85d1 in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb68b92cd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb6bf8dec in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb694c263 in QButton::mouseReleaseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb68f1390 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb6859547 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb685a47b in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0xb6f9ce03 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #22 0xb67f8e72 in QETWidget::translateMouseEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0xb67f8046 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0xb680868a in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0xb6870368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #26 0xb685906f in QApplication::enter_loop () from /usr/lib/qt3/lib/libqt-mt.so.3 #27 0xb6a3ed55 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #28 0xb37d4507 in Plugin_MetadataEdit::slotEditIptc () from /opt/kde3/lib/kde3/kipiplugin_metadataedit.so #29 0xb37d615e in Plugin_MetadataEdit::qt_invoke () from /opt/kde3/lib/kde3/kipiplugin_metadataedit.so #30 0xb68b866d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #31 0xb68b92cd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb7182da9 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4 #33 0xb71c5282 in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4 #34 0xb7289e2f in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 #35 0xb68b866d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb68b92cd in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb6eb8b69 in KAccelPrivate::menuItemActivated () from /opt/kde3/lib/libkdecore.so.4 #38 0xb6f088c7 in KAccelPrivate::emitActivatedSignal () from /opt/kde3/lib/libkdecore.so.4 #39 0xb6f4f239 in KAccelPrivate::eventFilter () from /opt/kde3/lib/libkdecore.so.4 #40 0xb68b7f6c in QObject::activate_filters () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0xb68b7fdb in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #42 0xb68f101c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #43 0xb69abfc2 in QMainWindow::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #44 0xb6859547 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #45 0xb685a8a2 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #46 0xb6f9ce03 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #47 0xb6f15082 in KAccelEventHandler::x11Event () from /opt/kde3/lib/libkdecore.so.4 #48 0xb6f9b26b in KApplication::x11EventFilter () from /opt/kde3/lib/libkdecore.so.4 #49 0xb67e7e54 in qt_x11EventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #50 0xb67f77d3 in QApplication::x11ProcessEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #51 0xb680868a in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #52 0xb6870368 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #53 0xb68701fe in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #54 0xb68590ff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #55 0x0804aa49 in main () _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-17 03:10 ------- Caspar, Thanks for your feedback; please hang on... Gilles, In kipi-plugins/metadataedit/iptceditdialog.cpp: void IPTCEditDialog::slotApply() { if (d->modified && !d->isReadOnly) { ... KIPIPlugins::Exiv2Iface exiv2Iface; exiv2Iface.load((*d->currItem).path()); exiv2Iface.setExif(d->iptcData); ^^^^^^^ exiv2Iface.save((*d->currItem).path()); d->modified = false; } } That should be setIptc, shouldn't it? Does this explain why Caspar says his Exif data is lost? -ahu. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-17 03:20 ------- Created an attachment (id=18591) --> (http://bugs.kde.org/attachment.cgi?id=18591&action=view) Updated Exiv2Iface test driver Try to simulate setting an IPTC caption using digikam's IPTC editor. However, this runs fine here and Valgrind doesn't report any problem. Can somebody who understands exactly what digikam is doing verify that the test driver does the same thing? If you get it to crash or Valgrind to find something wrong, please report. -ahu. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-17 03:51 ------- If I run the updated test driver with that suspicious setExif call instead of setIptc it crashes with a backtrace similar to that above. -ahu. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-17 06:58 ------- And what happens is this: In setExif, the call to d->exifMetadata.load() does not succeed (as expected, since it's called with IPTC data), and returns 1 to indicate a problem, which the caller does not test. Instead it assumes everything is fine, but d->exifMetadata is in an inconsistent state now, which causes the subsequent Image::writeMetadata call to crash. bool Exiv2Iface::setExif(const QByteArray& data) { try { if (!data.isEmpty()) { d->exifMetadata.load((const Exiv2::byte*)data.data(), data.size()); ^---------------- test if return value is 0 return true; } } catch( Exiv2::Error &e ) ... -ahu _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from mikmach@wp.pl
Mikolaj
Please post on B.K.O file, not on ML directly. thanks in advance Gilles > :( > > exiv2 984, kipi-plugins 605460, digikam 605459 > Crash when applying data on single image. There is no crash when > walking through several selected images, but data isn't applied. > > Using host libthread_db library "/lib/tls/libthread_db.so.1". > `shared object read from target memory' has disappeared; keeping its > symbols. > [Thread debugging using libthread_db enabled] > [New Thread -1239930560 (LWP 13823)] > [KCrash handler] > #5 0xffffe410 in __kernel_vsyscall () > #6 0xb61adef1 in raise () from /lib/tls/libc.so.6 > #7 0xb61af83b in abort () from /lib/tls/libc.so.6 > #8 0xb61e3ff5 in __fsetlocking () from /lib/tls/libc.so.6 > #9 0xb61ea587 in malloc_usable_size () from /lib/tls/libc.so.6 > #10 0xb61eaa02 in free () from /lib/tls/libc.so.6 > #11 0xb63936f1 in operator delete () from /usr/lib/libstdc++.so.6 > #12 0xb79a88ba in ~ValueType (this=0x1be50000) > > at > /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ex >t/new_allocator.h:94 #13 0xb79ae3a3 in ~Exifdatum (this=0x86be288) > > at > /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/me >mory:259 #14 0xb79b55bb in std::_Destroy<Exiv2::Exifdatum*, > std::allocator<Exiv2::Exifdatum> > (__first=0x86be294, __last=0x86be54c, > __alloc=@0xbfab53db) > > at > /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ex >t/new_allocator.h:107 #15 0xb79ae692 in ~ExifData (this=0x869ea64) > > at > /usr/lib/gcc/i586-mandriva-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bi >ts/stl_vector.h:273 #16 0xb79c8577 in ~JpegImage (this=0x869ea58) at > jpgimage.hpp:123 > #17 0xb4f1c8f1 in KIPIPlugins::Exiv2Iface::save () > from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so > #18 0xb4efa279 in KIPIMetadataEditPlugin::IPTCEditDialog::slotApply () > from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so > #19 0xb738ba8c in KDialogBase::qt_invoke () > from /usr/local/kde/lib/libkdeui.so.4 > #20 0xb4efa043 in KIPIMetadataEditPlugin::IPTCEditDialog::qt_invoke () > from /usr/local/kde/lib/kde3/kipiplugin_metadataedit.so > #21 0xb6a361bf in QObject::activate_signal () > from /usr/lib/qt3/lib/libqt-mt.so.3 > #22 0x0864fbb8 in ?? () > #23 0xbfab5574 in ?? () > #24 0x00000000 in ?? () > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 08:15 ------- #42 : fixed on svn Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 08:18 ------- #45 : ok . Idem with setIptc() method ? Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 08:32 ------- Andreas, Exiv2::IptcData::load() seem to return 0 or 1 like Exiv2::ExifData::load(). Fixed in svn, but it's not clear in Exiv2 API doc... Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From ahuggel gmx net 2006-11-17 08:40 ------- AFAICS IptcData::load returns 0 or 5 just as documented. -ahu. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 10:53 ------- #49 ==> right... Exiv2 API doc come from an old release. sorry (:=)) Fixed again in svn Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 10:58 ------- Andreas, i have fixed too the DMetadata class methods in digiKam core. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 11:10 ------- Hi guys, We need a feedback from you about this problem. Andreas have fixed current Exiv2 implementation, and me the Exiv2 interface from kipi-plugins and digiKam. To test, you need to checkout Exiv2/digiKam/kipi-plugins from svn repository. Compile and Install Exiv2 in first and cleanup digiKam/kipi-plugins before to recompile and install it. Thanks in advance Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
On Fri, 17 Nov 2006, Gilles Caulier wrote:
> To test, you need to checkout Exiv2/digiKam/kipi-plugins from svn repository. > > Compile and Install Exiv2 in first and cleanup digiKam/kipi-plugins before to recompile and install it. Using the script at http://www.digikam.org/?q=download/svn I get the following compile error Making all in libkipiplugins make[4]: Entering directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common/libkipiplugins' if /bin/sh ../../../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../li bkipi/libkipi -I../../../kipi-plugins/common/include -I../../../kipi-plugins/common/e xiv2iface -I../../../libkipi -I../../../libkipi -I/usr/include/kde -I/usr/share/qt3/include -I/usr/X11R6/include -I/home/abaecker/NBB/SOFTWARE/digikam/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D _XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -Wformat- security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NA MESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kpaboutdata.lo -MD -MP -MF ".deps/kpaboutdata.Tpo" \ -c -o kpaboutdata.lo `test -f 'kpaboutdata.cpp' || echo './'`kpaboutdata.cpp; \ then mv -f ".deps/kpaboutdata.Tpo" ".deps/kpaboutdata.Plo"; \ else rm -f ".deps/kpaboutdata.Tpo"; exit 1; \ fi kpaboutdata.cpp: In constructor `KIPIPlugins::KPAboutData::KPAboutData(const char*, const char*, int, const char*, const char*)': kpaboutdata.cpp:51: error: invalid use of undefined type `struct QImage' /usr/share/qt3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage' kpaboutdata.cpp:51: error: `setProgramLogo' undeclared (first use this function) kpaboutdata.cpp:51: error: (Each undeclared identifier is reported only once for each function it appears in.) make[4]: *** [kpaboutdata.lo] Error 1 make[4]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common/libkipiplugins' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/NEWTRYSVNALL/libs' make: *** [all] Error 2 I know that my debian sarge system is a bit outdated ;-), but I compiled this successfully in the not too distant past. (i.e. is the above a bug, or just a problem with my system, e.g. does kipi-plugins require KDE>3.3 ?) Best, Arnd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From arnd.baecker web de 2006-11-17 12:03 ------- On Fri, 17 Nov 2006, Gilles Caulier wrote: > To test, you need to checkout Exiv2/digiKam/kipi-plugins from svn repository. > > Compile and Install Exiv2 in first and cleanup digiKam/kipi-plugins before to recompile and install it. Using the script at http://www.digikam.org/?q=download/svn I get the following compile error Making all in libkipiplugins make[4]: Entering directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common/libkipiplugins' if /bin/sh ../../../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../li bkipi/libkipi -I../../../kipi-plugins/common/include -I../../../kipi-plugins/common/e xiv2iface -I../../../libkipi -I../../../libkipi -I/usr/include/kde -I/usr/share/qt3/include -I/usr/X11R6/include -I/home/abaecker/NBB/SOFTWARE/digikam/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D _XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -Wformat- security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NA MESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kpaboutdata.lo -MD -MP -MF ".deps/kpaboutdata.Tpo" \ -c -o kpaboutdata.lo `test -f 'kpaboutdata.cpp' || echo './'`kpaboutdata.cpp; \ then mv -f ".deps/kpaboutdata.Tpo" ".deps/kpaboutdata.Plo"; \ else rm -f ".deps/kpaboutdata.Tpo"; exit 1; \ fi kpaboutdata.cpp: In constructor `KIPIPlugins::KPAboutData::KPAboutData(const char*, const char*, int, const char*, const char*)': kpaboutdata.cpp:51: error: invalid use of undefined type `struct QImage' /usr/share/qt3/include/qwindowdefs.h:74: error: forward declaration of `struct QImage' kpaboutdata.cpp:51: error: `setProgramLogo' undeclared (first use this function) kpaboutdata.cpp:51: error: (Each undeclared identifier is reported only once for each function it appears in.) make[4]: *** [kpaboutdata.lo] Error 1 make[4]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common/libkipiplugins' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/NEWTRYSVNALL/libs/kipi-plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/NEWTRYSVNALL/libs' make: *** [all] Error 2 I know that my debian sarge system is a bit outdated ;-), but I compiled this successfully in the not too distant past. (i.e. is the above a bug, or just a problem with my system, e.g. does kipi-plugins require KDE>3.3 ?) Best, Arnd _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by Bugzilla from cmaessen@casco.demon.nl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=136855 ------- Additional Comments From caulier.gilles kdemail net 2006-11-17 12:09 ------- in kipi-plugins : - svn up, - make -f Makefile.cvs - ./configure ... - make ==> work fine here using automake, not unsermake... Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |