Summary: | media-gfx/digikam-0.9.0_beta1-r1 complains about -fno-exceptions | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick <mail> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.kde.org/show_bug.cgi?id=133525 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge digikam > digikam.log 2>&1
emerge -epvt digikam > epvt-digikam.log |
Description
Patrick
2006-09-01 12:01:42 UTC
Same issue described here: http://mail.kde.org/pipermail/digikam-users/2006-July/001812.html Please, paste the output of 'emerge -pvt exiv2 digikam' $ sudo emerge -pvt exiv2 digikam These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild U ] media-gfx/digikam-0.9.0_beta1-r1 [0.8.2] USE="arts exif%* -debug -doc -kdehiddenvisibility -nfs -xinerama" LINGUAS="de zh_CN -bg -bn -br -ca -cs -cy -da -el -en_GB -es -et -eu -fi -fr -ga -gl -he -hu -is -it -ja -km -lt -mk -ms -mt -nb -nl -nn -pa -pl -pt -pt_BR -ro -ru -rw -sl -sr -sr@Latn -sv -ta -tr -uk -vi" 0 kB [ebuild R ] media-gfx/exiv2-0.10-r1 USE="unicode -doc" 0 kB Total size of downloads: 0 kB I think that the failure does not happen because of the use of -fno-exceptions. It's just telling you that exception handling is disabled. The error you are describing has something to do with exiv, however I can't reproduce it. Hmm... I also tried to re-merge exiv2, didn't change anything. Do you have any ideas what else I could try? I'd really like to use digikam-0.9, 0.8 is a bit crashy here, and I hope it's better with the new version. (In reply to comment #4) > I think that the failure does not happen because of the use of -fno-exceptions. > It's just telling you that exception handling is disabled. > > The error you are describing has something to do with exiv, however I can't > reproduce it. > Does 'USE="-exif" emerge digikam' work for you? Well, that shouldn't be a question, it will work for you, but you'll lack exif support. Due to the fact that this looks a dependency problem to me, I'd like to ask you to ask for assistance upstream as I am unable to see what you are missing. But before you do that, please paste the output of "emerge -pvt =x11-libs/qt-3*" so that we can check that you have sqlite support enabled. No...
# USE="-exif" emerge -avu digikam
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] media-gfx/digikam-0.9.0_beta1-r1 [0.8.2] USE="arts -debug -doc -exif% -kdehiddenvisibility -nfs -xinerama" LINGUAS="de zh_CN -bg -bn -br -ca -cs -cy -da -el -en_GB -es -et -eu -fi -fr -ga -gl -he -hu -is -it -ja -km -lt -mk -ms -mt -nb -nl -nn -pa -pl -pt -pt_BR -ro -ru -rw -sl -sr -sr@Latn -sv -ta -tr -uk -vi" 0 kB
Total size of downloads: 0 kB
Would you like to merge these packages? [Yes/No] y
>>> Emerging (1 of 1) media-gfx/digikam-0.9.0_beta1-r1 to /
[...]
/bin/sh ../../../../libtool --silent --tag=CC --mode=compile i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -I../../../../digikam/libs/dimg -I../../../../digikam/libs/dmetadata -I../../../../digikam/libs/dcraw -I../../../../digikam/digikam -I../../../../digikam -DQT_THREAD_SUPPORT -D_REENTRANT -std=iso9899:1990 -W -Wall -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -DNDEBUG -O2 -O2 -march=pentium-m -msse3 -funroll-loops -Wformat-security -Wmissing-format-attribute -c -o iccjpeg.lo iccjpeg.c
In file included from ../../../../digikam/digikam/digikam_export.h:25,
from ../../../../digikam/libs/dimg/dimg.h:36,
from jpegloader.cpp:52:
../../../../config.h:56:1: warning: "HAVE_STDLIB_H" redefined
In file included from /usr/include/jpeglib.h:28,
from iccjpeg.h:43,
from jpegloader.cpp:33:
/usr/include/jconfig.h:12:1: warning: this is the location of the previous definition
jpegloader.cpp:75: warning: unused parameter 'msg_level'
/bin/sh ../../../../libtool --silent --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../../.. -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -I../../../../digikam/libs/dimg -I../../../../digikam/libs/dmetadata -I../../../../digikam/libs/dcraw -I../../../../digikam/digikam -I../../../../digikam -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -march=pentium-m -msse3 -funroll-loops -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -c -o rawloader.lo rawloader.cpp
/usr/local/include/exiv2/exif.hpp: In member function 'virtual const Exiv2::Value& Exiv2::Exifdatum::value() const':
/usr/local/include/exiv2/exif.hpp:287: error: exception handling disabled, use -fexceptions to enable
make[5]: *** [tiffloader.lo] Fehler 1
make[5]: *** Warte auf noch nicht beendete Prozesse...
make[5]: Leaving directory `/var/tmp/portage/digikam-0.9.0_beta1-r1/work/digikam-0.9.0-beta1/digikam/libs/dimg/loaders'
make[4]: *** [all-recursive] Fehler 1
make[4]: Leaving directory `/var/tmp/portage/digikam-0.9.0_beta1-r1/work/digikam-0.9.0-beta1/digikam/libs/dimg'
make[3]: *** [all-recursive] Fehler 1
make[3]: Leaving directory `/var/tmp/portage/digikam-0.9.0_beta1-r1/work/digikam-0.9.0-beta1/digikam/libs'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/var/tmp/portage/digikam-0.9.0_beta1-r1/work/digikam-0.9.0-beta1/digikam'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/var/tmp/portage/digikam-0.9.0_beta1-r1/work/digikam-0.9.0-beta1'
make: *** [all] Fehler 2
!!! ERROR: media-gfx/digikam-0.9.0_beta1-r1 failed.
Call stack:
ebuild.sh, line 1543: Called dyn_compile
ebuild.sh, line 938: Called src_compile
digikam-0.9.0_beta1-r1.ebuild, line 82: Called kde_src_compile
kde.eclass, line 166: Called kde_src_compile 'all'
kde.eclass, line 325: Called kde_src_compile 'myconf' 'configure' 'make'
kde.eclass, line 321: Called die
sqlite is disabled. Should I enable it and try again? # emerge -pvt =x11-libs/qt-3* These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild R ] x11-libs/qt-3.3.6-r1 USE="cups gif opengl -debug -doc -examples -firebird -immqt -immqt-bc -ipv6 -mysql -nas -nis -odbc -postgres -sqlite -xinerama" 14,224 kB Total size of downloads: 14,224 kB (In reply to comment #9) > sqlite is disabled. Should I enable it and try again? > > # emerge -pvt =x11-libs/qt-3* > > These are the packages that would be merged, in reverse order: > > Calculating dependencies... done! > [ebuild R ] x11-libs/qt-3.3.6-r1 USE="cups gif opengl -debug -doc > -examples -firebird -immqt -immqt-bc -ipv6 -mysql -nas -nis -odbc -postgres > -sqlite -xinerama" 14,224 kB > > Total size of downloads: 14,224 kB > That is the reason why you are getting this error. If you have the 'exif' USE flag enabled, you need Qt version 3 compiled with the 'sqlite' USE flag as well. If you emerge sync and try to emerge digikam, you should be able to see a new revision (digikam-0.9.2_beta1-r2) that will enforce such behaviour. So what you have to do is: 1. echo "=x11-libs/qt-3* sqlite" >> /etc/portage/package.use 2. emerge -uDN world 3. emerge digikam After you have done all that, it should work. If it does not, please reopen again. Still, it is well known that exif support for digikam will not work if you don't have sqlite support for qt 3. "Still, it is well known that exif support for digikam will not work if you don't have sqlite support for qt 3." I didn't know that, and I think you can't expect anybody to know such details. This should really be solved by dependencies or a break + information what to do when the useflag isn't set. And about the problem still existed even when exif was disabled? Where could the problem be here? The -r2 ebuild doesn't change anything for me. Still getting the same error. No new dependency and no warning or anthing like that. I enabled sqlite for qt-3 now and recompiled qt-3, still the same. And even if it would have worked, I would have reopened that bug, because it's not been resolved at all, and I also wouldn't regard this bug report as "INVALID". Cheers, Patrick. (In reply to comment #11). > "Still, it is well known that exif support for digikam will not work if > you don't have sqlite support for qt 3." > > I didn't know that, and I think you can't expect anybody to know such details. > This should really be solved by dependencies or a break + information what to > do when the useflag isn't set. It's in the ebuild itself. > > And about the problem still existed even when exif was disabled? Where could > the problem be here? Exif does nothing for this version of digikam, that's why. Exiv2 is a mandatory dependency, so that USE flag needs removal anyway. > > The -r2 ebuild doesn't change anything for me. Still getting the same error. > No new dependency and no warning or anthing like that. > The new revision checks that qt-3 has been compiled with sqlite support. If you tried to emerge -r2 after recompiling QT, obviously the ebuild will not die. > I enabled sqlite for qt-3 now and recompiled qt-3, still the same. And even if > it would have worked, I would have reopened that bug, because it's not been > resolved at all, and I also wouldn't regard this bug report as "INVALID". The bug itself is invalid if there's a wrong QT compilation. I need you to attach: 'emerge -epvt digikam' and 'emerge digikam > digikam.log 2>&1' I've had a talk with another person of the herd and apparently this is could be a bug with the application itself because exiv uses extensions and kde forces -fno-extension. Could you please report it upstream and paste 'emerge digikam > digikam.log 2>&1' in the bug you open? Please, also paste the link to the bug in here so that we can track it. Created attachment 95822 [details]
emerge digikam > digikam.log 2>&1
Created attachment 95823 [details]
emerge -epvt digikam > epvt-digikam.log
(In reply to comment #13) > I've had a talk with another person of the herd and apparently this is could be > a bug with the application itself because exiv uses extensions and kde forces > -fno-extension. Could you please report it upstream and paste > > 'emerge digikam > digikam.log 2>&1' > > in the bug you open? Please, also paste the link to the bug in here so that we > can track it. > Do you mean -fno-exception or -fno-extension? (In reply to comment #16) > Do you mean -fno-exception or -fno-extension? -fno-exception ... such things happen late at night :) I submitted a bug upstream. See https://bugs.kde.org/show_bug.cgi?id=133525 Do you think this would fix it (and could be made available through portage), so that 0.9.0 beta would finally be "testable" within gentoo? from bugs.kde.org: ------- Additional Comment #1 From Gilles Caulier 2006-09-04 08:06 ------- SVN commit 580635 by cgilles: digiKam from trunk: fix C++ Exception rules require by Exiv2 library BUG: 133525 M +1 -0 Makefile.am --- trunk/extragear/graphics/digikam/libs/dimg/loaders/Makefile.am #580634:580635 at at -1,4 +1,5 at at METASOURCES = AUTO +KDE_CXXFLAGS = $(USE_EXCEPTIONS) noinst_LTLIBRARIES = libdimgloaders.la That patch was already included in digikam-0.9.0-beta2. Did you try digikam-0.9.0-beta2 to see if it is reproducible? Yes, I tried -beta2, still this: /bin/sh ../../../libtool --silent --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -I/usr/kde/3.5/include -I../../../digikam/libs/dimg/loaders -I../../../digikam/libs/dimg/filters -I../../../digikam/libs/dmetadata -I../../../digikam/libs/dcraw -I../../../digikam/digikam -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 -DNDEBUG -DNO_DEBUG -O2 -O2 -march=pentium-m -msse3 -funroll-loops -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -c -o dcolorcomposer.lo dcolorcomposer.cpp /usr/local/include/exiv2/exif.hpp: In member function 'virtual const Exiv2::Value& Exiv2::Exifdatum::value() const': /usr/local/include/exiv2/exif.hpp:287: error: exception handling disabled, use -fexceptions to enable You'll have to tell in your bug upstream that the solution they proposed did not fix it for you. They might want the compilation log again. Sorry, just found out that I had cruft from a former Exiv2-installation in /usr/local/include/exiv2 (which is obvious, if you look at my error messages, but I seem to have been blind). |