yatc = yet another trouble compiling ;-)
I thought I'd give the newer versions a go, since I was running digikam 0.9.5 svn from a while ago... Starting with exiv2 0.18, configure/make/install went well. then libkexiv2-0.1.7, configure went well, but then I got this: (see bottom) I think it's got a problem with exiv2, but I'm not sure... I'm running kubuntu 8.04.1, so kde 3.5.10 Any suggestions for me to try? tnx Simon ----------------- make all-recursive make[1]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7' Making all in libkexiv2 make[2]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2' Making all in libkexiv2 make[3]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2/libkexiv2' /bin/bash ../../libtool --silent --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -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_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kexiv2.lo -MD -MP -MF .deps/kexiv2.Tpo -c -o kexiv2.lo kexiv2.cpp kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getExif() const': kexiv2.cpp:221: error: 'class Exiv2::ExifData' has no member named 'copy' kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getIptc(bool) const': kexiv2.cpp:258: error: 'class Exiv2::IptcData' has no member named 'copy' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExif(const QByteArray&)': kexiv2.cpp:289: error: 'class Exiv2::ExifData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setIptc(const QByteArray&)': kexiv2.cpp:312: error: 'class Exiv2::IptcData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExif(Exiv2::DataBuf)': kexiv2.cpp:335: error: 'class Exiv2::ExifData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setIptc(Exiv2::DataBuf)': kexiv2.cpp:358: error: 'class Exiv2::IptcData' has no member named 'load' kexiv2.cpp: In member function 'QImage KExiv2Iface::KExiv2::getExifThumbnail(bool) const': kexiv2.cpp:617: error: 'class Exiv2::ExifData' has no member named 'copyThumbnail' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExifThumbnail(const QImage&, bool)': kexiv2.cpp:697: error: 'class Exiv2::ExifData' has no member named 'setJpegThumbnail' kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getExifTagData(const char*) const': kexiv2.cpp:1292: error: 'class Exiv2::ExifData' has no member named 'byteOrder' make[3]: *** [kexiv2.lo] Error 1 make[3]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2/libkexiv2' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7' make: *** [all] Error 2 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Dnia Wednesday 31 December 2008, Simon Oosthoek napisał:
> yatc = yet another trouble compiling ;-) > > I thought I'd give the newer versions a go, since I was running digikam > 0.9.5 svn from a while ago... > > Starting with exiv2 0.18, configure/make/install went well. > > then libkexiv2-0.1.7, configure went well, but then I got this: (see > bottom) > > I think it's got a problem with exiv2, but I'm not sure... > > I'm running kubuntu 8.04.1, so kde 3.5.10 > > Any suggestions for me to try? You probably have two version of exiv2 on your computer: one from package and one compiled by yourself. Enforce removing of package and problems should vanish. m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Mikolaj Machowski wrote:
> Dnia Wednesday 31 December 2008, Simon Oosthoek napisał: >> yatc = yet another trouble compiling ;-) >> >> I thought I'd give the newer versions a go, since I was running digikam >> 0.9.5 svn from a while ago... >> >> Starting with exiv2 0.18, configure/make/install went well. >> >> then libkexiv2-0.1.7, configure went well, but then I got this: (see >> bottom) >> >> I think it's got a problem with exiv2, but I'm not sure... >> >> I'm running kubuntu 8.04.1, so kde 3.5.10 >> >> Any suggestions for me to try? > > You probably have two version of exiv2 on your computer: one from > package and one compiled by yourself. Enforce removing of package and > problems should vanish. > Actually, I did try that, but perhaps I need to be more thorough? I'll give it another try when I have some more time/attention for it ;-) Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Simon Oosthoek wrote:
> Mikolaj Machowski wrote: >> Dnia Wednesday 31 December 2008, Simon Oosthoek napisał: >>> yatc = yet another trouble compiling ;-) >>> >>> I thought I'd give the newer versions a go, since I was running digikam >>> 0.9.5 svn from a while ago... >>> >>> Starting with exiv2 0.18, configure/make/install went well. >>> >>> then libkexiv2-0.1.7, configure went well, but then I got this: (see >>> bottom) >>> >>> I think it's got a problem with exiv2, but I'm not sure... >>> >>> I'm running kubuntu 8.04.1, so kde 3.5.10 >>> >>> Any suggestions for me to try? >> You probably have two version of exiv2 on your computer: one from >> package and one compiled by yourself. Enforce removing of package and >> problems should vanish. >> > > Actually, I did try that, but perhaps I need to be more thorough? > I'll give it another try when I have some more time/attention for it ;-) > This time I thorougly removed all exiv2 related packages, files and directories from /usr (except the libkexiv2 related files, since I figured they would be overwritten and were not required for compiling libkexiv2-0.1.7) Then I installed exiv2-0.18 from the compiled sources and this is what I get when doing a find /usr -name "*exiv2*": /usr/include/libkexiv2 /usr/include/libkexiv2/kexiv2.h /usr/include/libkexiv2/libkexiv2_export.h /usr/lib/pkgconfig/libkexiv2.pc /usr/lib/libkexiv2.so.5.0.0 /usr/lib/libkexiv2.so.3.1.0 /usr/lib/libkexiv2.so.3 /usr/lib/libkexiv2.so /usr/lib/libkexiv2.la /usr/lib/libkexiv2.so.5 /usr/local/bin/exiv2 /usr/local/include/exiv2 /usr/local/lib/pkgconfig/exiv2.pc /usr/local/lib/libexiv2.so.5.2.0 /usr/local/lib/libexiv2.so.5 /usr/local/lib/libexiv2.so /usr/local/lib/libexiv2.la /usr/local/lib/libexiv2.a /usr/local/share/man/man1/exiv2.1 /usr/local/share/locale/de/LC_MESSAGES/exiv2.mo /usr/local/share/locale/pl/LC_MESSAGES/exiv2.mo /usr/local/share/locale/fr/LC_MESSAGES/exiv2.mo /usr/local/share/locale/ru/LC_MESSAGES/exiv2.mo /usr/local/share/locale/sk/LC_MESSAGES/exiv2.mo /usr/local/share/locale/es/LC_MESSAGES/exiv2.mo /usr/local/share/locale/fi/LC_MESSAGES/exiv2.mo After running configure, I still get the compile errors from libkexiv2: make all-recursive make[1]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7' Making all in libkexiv2 make[2]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2' Making all in libkexiv2 make[3]: Entering directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2/libkexiv2' /bin/bash ../../libtool --silent --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -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_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -MT kexiv2.lo -MD -MP -MF .deps/kexiv2.Tpo -c -o kexiv2.lo kexiv2.cpp kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getExif() const': kexiv2.cpp:221: error: 'class Exiv2::ExifData' has no member named 'copy' kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getIptc(bool) const': kexiv2.cpp:258: error: 'class Exiv2::IptcData' has no member named 'copy' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExif(const QByteArray&)': kexiv2.cpp:289: error: 'class Exiv2::ExifData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setIptc(const QByteArray&)': kexiv2.cpp:312: error: 'class Exiv2::IptcData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExif(Exiv2::DataBuf)': kexiv2.cpp:335: error: 'class Exiv2::ExifData' has no member named 'load' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setIptc(Exiv2::DataBuf)': kexiv2.cpp:358: error: 'class Exiv2::IptcData' has no member named 'load' kexiv2.cpp: In member function 'QImage KExiv2Iface::KExiv2::getExifThumbnail(bool) const': kexiv2.cpp:617: error: 'class Exiv2::ExifData' has no member named 'copyThumbnail' kexiv2.cpp: In member function 'bool KExiv2Iface::KExiv2::setExifThumbnail(const QImage&, bool)': kexiv2.cpp:697: error: 'class Exiv2::ExifData' has no member named 'setJpegThumbnail' kexiv2.cpp: In member function 'QByteArray KExiv2Iface::KExiv2::getExifTagData(const char*) const': kexiv2.cpp:1292: error: 'class Exiv2::ExifData' has no member named 'byteOrder' make[3]: *** [kexiv2.lo] Error 1 make[3]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2/libkexiv2' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7/libkexiv2' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/simon/src/kde3/libkexiv2-0.1.7' make: *** [all] Error 2 To me, it's pretty rare that packages don't compile after running configure like this. So I guess there's a bug somewhere... I hope someone can give me a hint to look further into this problem! Thnx Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Dnia Saturday 03 January 2009, Simon Oosthoek napisał:
> > To me, it's pretty rare that packages don't compile after running > configure like this. So I guess there's a bug somewhere... > > I hope someone can give me a hint to look further into this problem! For me it looks like there is still some conflict between versions. Hmm. Are you recompiling from old directory? Try to remove kexiv2 dir, unpack sources and compile completely from scratch. Maybe some files are in cache? m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Mikolaj Machowski wrote:
> Dnia Saturday 03 January 2009, Simon Oosthoek napisał: >> To me, it's pretty rare that packages don't compile after running >> configure like this. So I guess there's a bug somewhere... >> >> I hope someone can give me a hint to look further into this problem! > > For me it looks like there is still some conflict between versions. Hmm. > Are you recompiling from old directory? Try to remove kexiv2 dir, unpack > sources and compile completely from scratch. Maybe some files are in > cache? > I removed the libkexiv2 source dir and unpacked again, ./configure && make; same problem! I'm not too familiar with the internals of the configure script, but perhaps I can distil some meaning from the config.log... > configure:33633: result: yes > configure:33710: checking for exiv2 >= 0.12 shouldn't this be 0.18 or later if it requires the new API? > configure:33714: result: yes > configure:33718: checking EXIV2_CFLAGS > configure:33721: result: -I/usr/local/include > configure:33724: checking EXIV2_LIBS > configure:33727: result: -L/usr/local/lib -lexiv2 > configure:33908: creating ./config.status This bit does find the correct version of libexiv2, which I just installed from the sources... I don't see any other mentionings of libexiv2 in the config.log. Am I the only one having this trouble when compiling for kde3 on kubuntu 8.04.1? Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Simon Oosthoek wrote:
> Mikolaj Machowski wrote: >> Dnia Saturday 03 January 2009, Simon Oosthoek napisał: >>> To me, it's pretty rare that packages don't compile after running >>> configure like this. So I guess there's a bug somewhere... I did some further digging and I can see that the first error I get: kexiv2.cpp:221: error: 'class Exiv2::ExifData' has no member named 'copy' appears to be correct with the sources of exiv2 v0.18, because there is no member of class ExifData (defined in exiv2-0.18/src/exif.hpp:430-517) and it is explicitly used in libkexiv2-0.1.7/libkexiv2/libkexiv2/kexiv2.cpp:221 220 Exiv2::ExifData& exif = d->exifMetadata; 221 Exiv2::DataBuf c2 = exif.copy(); So I guess the compile errors I get are actually bugs for the currently released versions of exiv2 and libkexiv2? Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Simon Oosthoek wrote:
> Simon Oosthoek wrote: >> Mikolaj Machowski wrote: >>> Dnia Saturday 03 January 2009, Simon Oosthoek napisał: >>>> To me, it's pretty rare that packages don't compile after running >>>> configure like this. So I guess there's a bug somewhere... > > I did some further digging and I can see that the first error I get: > kexiv2.cpp:221: error: 'class Exiv2::ExifData' has no member named 'copy' > > appears to be correct with the sources of exiv2 v0.18, because there is > no member of class ExifData (defined in exiv2-0.18/src/exif.hpp:430-517) > and it is explicitly used in > libkexiv2-0.1.7/libkexiv2/libkexiv2/kexiv2.cpp:221 > > 220 Exiv2::ExifData& exif = d->exifMetadata; > 221 Exiv2::DataBuf c2 = exif.copy(); Could this have been intended to use Exiv2::ExifThumbC ? because this class does have a copy method: from exif.hpp: //! @name Accessors //@{ /*! @brief Return the thumbnail image in a %DataBuf. The caller owns the data buffer and %DataBuf ensures that it will be deleted. */ DataBuf copy() const; (last linenumber is 277) I'm totally at a loss now, I guess I'll reinstall libexiv2 0.16 from the kubuntu packages, since this isn't getting me further now... Cheers /Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Simon Oosthoek wrote:
> Simon Oosthoek wrote: >> Simon Oosthoek wrote: >>> Mikolaj Machowski wrote: >>>> Dnia Saturday 03 January 2009, Simon Oosthoek napisał: >>>>> To me, it's pretty rare that packages don't compile after running >>>>> configure like this. So I guess there's a bug somewhere... >> I did some further digging and I can see that the first error I get: >> kexiv2.cpp:221: error: 'class Exiv2::ExifData' has no member named 'copy' >> >> appears to be correct with the sources of exiv2 v0.18, because there is >> no member of class ExifData (defined in exiv2-0.18/src/exif.hpp:430-517) >> and it is explicitly used in >> libkexiv2-0.1.7/libkexiv2/libkexiv2/kexiv2.cpp:221 >> >> 220 Exiv2::ExifData& exif = d->exifMetadata; >> 221 Exiv2::DataBuf c2 = exif.copy(); > Apparently, this bit is quite different in the current libkexiv2 svn code, which does seem to compile just fine... I'm now compiling digikam 0.9.5 beta 2 (fingers crossed ;-) /Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Dnia Sunday 04 January 2009, Simon Oosthoek napisał:
> > Apparently, this bit is quite different in the current libkexiv2 svn > code, which does seem to compile just fine... > > I'm now compiling digikam 0.9.5 beta 2 (fingers crossed ;-) I completely don't know what is going on. As an encouragement I can only say that svn exiv2, svn libkexiv2 and svn digiKam 0.9.x is working fine together - just recompiled successfully. m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Mikolaj Machowski wrote:
> Dnia Sunday 04 January 2009, Simon Oosthoek napisał: >> Apparently, this bit is quite different in the current libkexiv2 svn >> code, which does seem to compile just fine... >> >> I'm now compiling digikam 0.9.5 beta 2 (fingers crossed ;-) > > I completely don't know what is going on. As an encouragement I can only > say that svn exiv2, svn libkexiv2 and svn digiKam 0.9.x is working fine > together - just recompiled successfully. > Same here, I compiled exiv2 0.18 and libkexiv2/digikam from svn and I have it all working again :-) But the combination of exiv2 0.18 and libkexiv2 0.1.7 doesn't seem to work (and I think I've shown that this can be verified in the sources, though my c++ is not that reliable ;-). Unfortunately, these are both released versions, which could be awkward for people trying to compile them together... Cheers Simon _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |