Hello,
I wanted to update to the latest svn versions yesterday, but I always got the configure message (althoug I've updated exiv2 before): digiKam needs Exiv2 library. You need to install Exiv2 first Exiv2 website is at http://www.exiv2.org A week or so ago everything went easy with the svn up, I havn't changed anything... So, today I deleted all the files and directories to restart from a clean basis. I run the 2 scripts compile_exiv2.sh and compile_digikam.sh but I still get this message. I've downloaded the scripts again from the digikam.org-site to check if there's something new in them, but the compare against my scripts with Kdiff3 shows no difference, except of my "DIGIKAMDEST"-path. I've put the complete output of the two compile_scripts here: http://www.daniel-bauer.com/test/compile_exiv2.sh.out.txt http://www.daniel-bauer.com/test/compile_digikam.sh.out.txt Of course I cannot find out anything in there... The only thing that catched my eye was a (part of a) script that seemed to be just displayed in the console, but not executed (I guess). It's at the end of the compile_exiv2.sh.out.txt. What can I do? Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
> Of course I cannot find out anything in there... The only thing that catched > my eye was a (part of a) script that seemed to be just displayed in the > console, but not executed (I guess). It's at the end of the > compile_exiv2.sh.out.txt. Nuke your SVN copy of Exiv2 from installation and build areas. Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. That worked for me. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Lundi 4 Décembre 2006 18:27, Duncan Hill a écrit :
> > Of course I cannot find out anything in there... The only thing that > > catched my eye was a (part of a) script that seemed to be just displayed > > in the console, but not executed (I guess). It's at the end of the > > compile_exiv2.sh.out.txt. > > Nuke your SVN copy of Exiv2 from installation and build areas. > Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. > That worked for me. > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users digikam and kipi-plugins require at least Exiv2 0.12 : http://www.digikam.org/?q=node/193 Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Caulier Gilles wrote:
> Le Lundi 4 Décembre 2006 18:27, Duncan Hill a écrit : >>> Of course I cannot find out anything in there... The only thing that >>> catched my eye was a (part of a) script that seemed to be just displayed >>> in the console, but not executed (I guess). It's at the end of the >>> compile_exiv2.sh.out.txt. >> Nuke your SVN copy of Exiv2 from installation and build areas. >> Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. >> That worked for me. >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > digikam and kipi-plugins require at least Exiv2 0.12 : > > http://www.digikam.org/?q=node/193 Yes. What I encountered was even with an svn up and reconfigure/rebuild of exiv2 from svn, it still installed as .10, not .12. I had to remove the entire build area and the installed libs and recompile from scratch. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Monday 04 December 2006 19:34, Duncan Hill wrote:
> Caulier Gilles wrote: > > Le Lundi 4 Décembre 2006 18:27, Duncan Hill a écrit : > >>> Of course I cannot find out anything in there... The only thing that > >>> catched my eye was a (part of a) script that seemed to be just > >>> displayed in the console, but not executed (I guess). It's at the end > >>> of the compile_exiv2.sh.out.txt. > >> > >> Nuke your SVN copy of Exiv2 from installation and build areas. > >> Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. > >> That worked for me. > >> _______________________________________________ > >> Digikam-users mailing list > >> [hidden email] > >> https://mail.kde.org/mailman/listinfo/digikam-users > > > > digikam and kipi-plugins require at least Exiv2 0.12 : > > > > http://www.digikam.org/?q=node/193 > > Yes. What I encountered was even with an svn up and reconfigure/rebuild > of exiv2 from svn, it still installed as .10, not .12. I had to remove > the entire build area and the installed libs and recompile from scratch. Ok, I kind of understand ;-) so, what do I exactly have to do to "nuke" my Exiv2 svn copy? I had already removed *all* directores/files within my "DIGIKAMDEST"-path and then let in completely reinstall with the compile_exiv2.sh script.... Must I do something additional to just deleting directories/files? (Remember: I use the scripts from "Install digiKam in your Home Directory" on http://www.digikam.org/?q=download/svn ) Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hi Daniel,
Daniel Bauer wrote: > On Monday 04 December 2006 19:34, Duncan Hill wrote: > >>Caulier Gilles wrote: >> >>>Le Lundi 4 Décembre 2006 18:27, Duncan Hill a écrit : >>> >>>>>Of course I cannot find out anything in there... The only thing that >>>>>catched my eye was a (part of a) script that seemed to be just >>>>>displayed in the console, but not executed (I guess). It's at the end >>>>>of the compile_exiv2.sh.out.txt. >>>> >>>>Nuke your SVN copy of Exiv2 from installation and build areas. >>>>Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. >>>>That worked for me. >>>>_______________________________________________ >>>>Digikam-users mailing list >>>>[hidden email] >>>>https://mail.kde.org/mailman/listinfo/digikam-users >>> >>>digikam and kipi-plugins require at least Exiv2 0.12 : >>> >>>http://www.digikam.org/?q=node/193 >> >>Yes. What I encountered was even with an svn up and reconfigure/rebuild >>of exiv2 from svn, it still installed as .10, not .12. I had to remove >>the entire build area and the installed libs and recompile from scratch. > > > Ok, I kind of understand ;-) > > so, what do I exactly have to do to "nuke" my Exiv2 svn copy? > I had already removed *all* directores/files within my "DIGIKAMDEST"-path and > then let in completely reinstall with the compile_exiv2.sh script.... > > Must I do something additional to just deleting directories/files? > > (Remember: I use the scripts from "Install digiKam in your Home Directory" on > http://www.digikam.org/?q=download/svn ) I sent an email about that on kde imaging list. With their new check for exiv2-0.12, it doesn't work by default because pkg-config can't find exiv2. There's a workaround : add this in the script (with other exports) : export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig I will add that on the digikam website -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 05 December 2006 09:52, Fabien wrote:
> Hi Daniel, > > Daniel Bauer wrote: > > On Monday 04 December 2006 19:34, Duncan Hill wrote: > >>Caulier Gilles wrote: > >>>Le Lundi 4 Décembre 2006 18:27, Duncan Hill a écrit : > >>>>>Of course I cannot find out anything in there... The only thing that > >>>>>catched my eye was a (part of a) script that seemed to be just > >>>>>displayed in the console, but not executed (I guess). It's at the end > >>>>>of the compile_exiv2.sh.out.txt. > >>>> > >>>>Nuke your SVN copy of Exiv2 from installation and build areas. > >>>>Re-checkout Exiv2 (or use the .12 tarball), recompile and reinstall. > >>>>That worked for me. > >>>>_______________________________________________ > >>>>Digikam-users mailing list > >>>>[hidden email] > >>>>https://mail.kde.org/mailman/listinfo/digikam-users > >>> > >>>digikam and kipi-plugins require at least Exiv2 0.12 : > >>> > >>>http://www.digikam.org/?q=node/193 > >> > >>Yes. What I encountered was even with an svn up and reconfigure/rebuild > >>of exiv2 from svn, it still installed as .10, not .12. I had to remove > >>the entire build area and the installed libs and recompile from scratch. > > > > Ok, I kind of understand ;-) > > > > so, what do I exactly have to do to "nuke" my Exiv2 svn copy? > > I had already removed *all* directores/files within my "DIGIKAMDEST"-path > > and then let in completely reinstall with the compile_exiv2.sh script.... > > > > Must I do something additional to just deleting directories/files? > > > > (Remember: I use the scripts from "Install digiKam in your Home > > Directory" on http://www.digikam.org/?q=download/svn ) > > I sent an email about that on kde imaging list. > With their new check for exiv2-0.12, it doesn't work by default because > pkg-config can't find exiv2. > There's a workaround : add this in the script (with other exports) : > export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig > > I will add that on the digikam website > > -- > Fabien Fabien, I've tried this, but no luck - configure still complains that there is no exiv2 although the path $DIGIKAMDEST/lib/pkgconfig exists and there are two files in there (exiv2.pc and libkipi.pc) ... I've deleted everything, entered export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig at the beginning of both compile... files run compile_exiv2.sh, then compile_digikam.sh. no luck, again deleted everything, deleted the new export command from the compile_exiv2.sh (but left it in compile_digikam.sh), still no luck. ??? Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Ok, I changed the website and the compile_digikam.txt script.
Daniel Bauer wrote: > On Tuesday 05 December 2006 09:52, Fabien wrote: >>I sent an email about that on kde imaging list. >>With their new check for exiv2-0.12, it doesn't work by default because >>pkg-config can't find exiv2. >>There's a workaround : add this in the script (with other exports) : >>export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig >> >>I will add that on the digikam website >> > > Fabien, I've tried this, but no luck - configure still complains that there is > no exiv2 although the path $DIGIKAMDEST/lib/pkgconfig exists and there are > two files in there (exiv2.pc and libkipi.pc) ... > > I've deleted everything, > entered export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig at the beginning of > both compile... files > run compile_exiv2.sh, then compile_digikam.sh. > no luck, > > again deleted everything, deleted the new export command from the > compile_exiv2.sh (but left it in compile_digikam.sh), still no luck. Note, only compile_digikam.txt needs to be changed. Could you try with the latest script and sent the one you used so we can check what's the problem ? I hope you didn't put the export PKG_CONFIG_PATH *before* the definition of $DIGIKAMDEST ;-) -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 05 December 2006 12:23, Fabien wrote:
> Ok, I changed the website and the compile_digikam.txt script. ... > > Note, only compile_digikam.txt needs to be changed. > Could you try with the latest script and sent the one you used so we can > check what's the problem ? > > I hope you didn't put the export PKG_CONFIG_PATH *before* the definition > of $DIGIKAMDEST ;-) hehe, could be possible :-) but no, I had it in the right place. Now, I have still no luck. Just to be sure I've downloaded the scripts again and used them for another try. Here's what I did: - deleted everything in /home/digi/digikamSVN and in /home/digi/digikam_svn - placed freshly downloaded scripts in /home/digi/digikam_svn - in console (as user daniel): su -l digi (+ password) cd digikam_svn ./compile_exiv2.sh >compile_exiv2.out.txt 2>&1 ./compile_digikam.sh >compile_digikam.out.txt 2>&1 Got the same errors.... One thing I wonder: while running compile_digikam, in the results for the Kipi_Plugins configure it says: -- Exiv2 library found............ YES but later in the same script, in the results for digiKam configure, it says: -- Exiv2 library found............ NO So it is as if it forgot where the Exiv2 library is during executing the script? I copied everything to my server, so you can see all the output. The above mentioned lines are 1243 (Yes) and 5087 (no) in the compile-digikam-output. I've also copied the used scripts on the server, but they should be exactly what I've downloaded except of the changed path... But you can check, if I messed up something, although I think I havn't. here's the ouput: http://www.daniel-bauer.com/test/compile_exiv2.out.txt http://www.daniel-bauer.com/test/compile_digikam.out.txt and the scripts: http://www.daniel-bauer.com/test/compile_exiv2.sh.txt http://www.daniel-bauer.com/test/compile_digikam.sh.txt b.t.w.: I wonder about the "/" at the end of the DIGIKAMDEST-path, because then sometimes I see "/home/digi/digikamSVN//" with two "/". However, I've also tried with leaving the final "/" away, didn't change anything. till later Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Daniel Bauer wrote:
> > [...] > - deleted everything in /home/digi/digikamSVN and in /home/digi/digikam_svn > - placed freshly downloaded scripts in /home/digi/digikam_svn > - in console (as user daniel): > su -l digi (+ password) > cd digikam_svn > ./compile_exiv2.sh >compile_exiv2.out.txt 2>&1 > ./compile_digikam.sh >compile_digikam.out.txt 2>&1 > > Got the same errors.... > > One thing I wonder: while running compile_digikam, in the results for the > Kipi_Plugins configure it says: > > -- Exiv2 library found............ YES > > but later in the same script, in the results for digiKam configure, it says: > > -- Exiv2 library found............ NO > > So it is as if it forgot where the Exiv2 library is during executing the > script? Not really. The check made in configure script doesn't return true. I wonder why, I can't reproduce it here... Can you try to run : pkg-config --debug --exists "exiv2 >= 0.12" after using the exports in your shell ? > I copied everything to my server, so you can see all the output. The above > mentioned lines are 1243 (Yes) and 5087 (no) in the compile-digikam-output. > I've also copied the used scripts on the server, but they should be exactly > what I've downloaded except of the changed path... But you can check, if I > messed up something, although I think I havn't. It looks ok. > b.t.w.: > I wonder about the "/" at the end of the DIGIKAMDEST-path, because then > sometimes I see "/home/digi/digikamSVN//" with two "/". However, I've also > tried with leaving the final "/" away, didn't change anything. This is what I was wondering. I also tried, but it still ok for me. Double // is allowed, so it shouldn't be a problem. Anyway, I will fix it on the website... Could you also put the graphics/config.log file in your website ? -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
Dear listers,
I just downloaded the complete bunch of files and have still problems getting the kipiplugins to compile. When I try to apply the disable ipod patch, I get [root@localhost digikam]# cd kipi-plugins-0.1.3-beta1 [root@localhost kipi-plugins-0.1.3-beta1]# patch < disable_ipod.patch patching file Makefile.am Hunk #1 FAILED at 21. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej Can someone help here please. I am a real noob so be patient please. Thanks David _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Fabien-5
On Tuesday 05 December 2006 15:26, Fabien wrote:
> > Can you try to run : > pkg-config --debug --exists "exiv2 >= 0.12" > > after using the exports in your shell ? Did you mean typing the export commands from the complie_digikam.sh script and then the above? If so, here's what I get: digi@venus:~> export DIGIKAMDEST=/home/digi/digikamSVN/ digi@venus:~> export KDEDIRS=$DIGIKAMDEST:/usr ; export LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export LDPATH=$DIGIKAMDEST/lib:$LDPATH digi@venus:~> export UNSERMAKE=no digi@venus:~> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig digi@venus:~> export PATH=$DIGIKAMDEST/bin:$PATH digi@venus:~> pkg-config --debug --exists "exiv2 >= 0.12" Option --debug seen Option --exists seen Error printing disabled by default, value of --print-errors: 0 Error printing disabled Adding virtual 'pkg-config' package to list of known packages Scanning directory '/home/digi/digikamSVN//lib/pkgconfig' Ignoring file '.' in search directory; not a .pc file Ignoring file '..' in search directory; not a .pc file File 'libkipi.pc' appears to be a .pc file Will find package 'libkipi' in file '/home/digi/digikamSVN//lib/pkgconfig/libkipi.pc' File 'exiv2.pc' appears to be a .pc file Will find package 'exiv2' in file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' Scanning directory '/usr/lib/pkgconfig' Ignoring file '.' in search directory; not a .pc file Ignoring file '..' in search directory; not a .pc file File 'openssl.pc' appears to be a .pc file Will find package 'openssl' in file '/usr/lib/pkgconfig/openssl.pc' File 'ext2fs.pc' appears to be a .pc file Will find package 'ext2fs' in file '/usr/lib/pkgconfig/ext2fs.pc' File 'libidn.pc' appears to be a .pc file Will find package 'libidn' in file '/usr/lib/pkgconfig/libidn.pc' File 'xcursor.pc' appears to be a .pc file Will find package 'xcursor' in file '/usr/lib/pkgconfig/xcursor.pc' File 'sqlite3.pc' appears to be a .pc file Will find package 'sqlite3' in file '/usr/lib/pkgconfig/sqlite3.pc' File 'Wand.pc' appears to be a .pc file Will find package 'Wand' in file '/usr/lib/pkgconfig/Wand.pc' File 'libwvfft.pc' appears to be a .pc file Will find package 'libwvfft' in file '/usr/lib/pkgconfig/libwvfft.pc' File 'gnutls.pc' appears to be a .pc file Will find package 'gnutls' in file '/usr/lib/pkgconfig/gnutls.pc' File 'freetype2.pc' appears to be a .pc file Will find package 'freetype2' in file '/usr/lib/pkgconfig/freetype2.pc' File 'ao.pc' appears to be a .pc file Will find package 'ao' in file '/usr/lib/pkgconfig/ao.pc' File 'libexif.pc' appears to be a .pc file Will find package 'libexif' in file '/usr/lib/pkgconfig/libexif.pc' File 'dbus-1.pc' appears to be a .pc file Will find package 'dbus-1' in file '/usr/lib/pkgconfig/dbus-1.pc' File 'libpng.pc' appears to be a .pc file Will find package 'libpng' in file '/usr/lib/pkgconfig/libpng.pc' File 'ss.pc' appears to be a .pc file Will find package 'ss' in file '/usr/lib/pkgconfig/ss.pc' File 'dbus-glib-1.pc' appears to be a .pc file Will find package 'dbus-glib-1' in file '/usr/lib/pkgconfig/dbus-glib-1.pc' File 'libscconf.pc' appears to be a .pc file Will find package 'libscconf' in file '/usr/lib/pkgconfig/libscconf.pc' File 'speex.pc' appears to be a .pc file Will find package 'speex' in file '/usr/lib/pkgconfig/speex.pc' File 'xcomposite.pc' appears to be a .pc file Will find package 'xcomposite' in file '/usr/lib/pkgconfig/xcomposite.pc' File 'imlib2.pc' appears to be a .pc file Will find package 'imlib2' in file '/usr/lib/pkgconfig/imlib2.pc' File 'libwvutils.pc' appears to be a .pc file Will find package 'libwvutils' in file '/usr/lib/pkgconfig/libwvutils.pc' File 'lcms.pc' appears to be a .pc file Will find package 'lcms' in file '/usr/lib/pkgconfig/lcms.pc' File 'esound.pc' appears to be a .pc file Will find package 'esound' in file '/usr/lib/pkgconfig/esound.pc' File 'wmlib.pc' appears to be a .pc file Will find package 'wmlib' in file '/usr/lib/pkgconfig/wmlib.pc' File 'WINGs.pc' appears to be a .pc file Will find package 'WINGs' in file '/usr/lib/pkgconfig/WINGs.pc' File 'libvcdinfo.pc' appears to be a .pc file Will find package 'libvcdinfo' in file '/usr/lib/pkgconfig/libvcdinfo.pc' File 'OpenEXR.pc' appears to be a .pc file Will find package 'OpenEXR' in file '/usr/lib/pkgconfig/OpenEXR.pc' File 'libgphoto2.pc' appears to be a .pc file Will find package 'libgphoto2' in file '/usr/lib/pkgconfig/libgphoto2.pc' File 'xrender.pc' appears to be a .pc file Will find package 'xrender' in file '/usr/lib/pkgconfig/xrender.pc' File 'vorbisenc.pc' appears to be a .pc file Will find package 'vorbisenc' in file '/usr/lib/pkgconfig/vorbisenc.pc' File 'mjpegtools.pc' appears to be a .pc file Will find package 'mjpegtools' in file '/usr/lib/pkgconfig/mjpegtools.pc' File 'openobex.pc' appears to be a .pc file Will find package 'openobex' in file '/usr/lib/pkgconfig/openobex.pc' File 'libscldap.pc' appears to be a .pc file Will find package 'libscldap' in file '/usr/lib/pkgconfig/libscldap.pc' File 'libuniconf.pc' appears to be a .pc file Will find package 'libuniconf' in file '/usr/lib/pkgconfig/libuniconf.pc' File 'glitz.pc' appears to be a .pc file Will find package 'glitz' in file '/usr/lib/pkgconfig/glitz.pc' File 'liboggvorbis.pc' appears to be a .pc file Will find package 'liboggvorbis' in file '/usr/lib/pkgconfig/liboggvorbis.pc' File 'xfixes.pc' appears to be a .pc file Will find package 'xfixes' in file '/usr/lib/pkgconfig/xfixes.pc' File 'fusion.pc' appears to be a .pc file Will find package 'fusion' in file '/usr/lib/pkgconfig/fusion.pc' File 'cairo.pc' appears to be a .pc file Will find package 'cairo' in file '/usr/lib/pkgconfig/cairo.pc' File 'fribidi.pc' appears to be a .pc file Will find package 'fribidi' in file '/usr/lib/pkgconfig/fribidi.pc' File 'blkid.pc' appears to be a .pc file Will find package 'blkid' in file '/usr/lib/pkgconfig/blkid.pc' File 'libcdio_cdda.pc' appears to be a .pc file Will find package 'libcdio_cdda' in file '/usr/lib/pkgconfig/libcdio_cdda.pc' File 'e2p.pc' appears to be a .pc file Will find package 'e2p' in file '/usr/lib/pkgconfig/e2p.pc' File 'ImageMagick.pc' appears to be a .pc file Will find package 'ImageMagick' in file '/usr/lib/pkgconfig/ImageMagick.pc' File 'samplerate.pc' appears to be a .pc file Will find package 'samplerate' in file '/usr/lib/pkgconfig/samplerate.pc' File 'sqlite.pc' appears to be a .pc file Will find package 'sqlite' in file '/usr/lib/pkgconfig/sqlite.pc' File 'libmusicbrainz.pc' appears to be a .pc file Will find package 'libmusicbrainz' in file '/usr/lib/pkgconfig/libmusicbrainz.pc' File 'limal-bootloader.pc' appears to be a .pc file Will find package 'limal-bootloader' in file '/usr/lib/pkgconfig/limal-bootloader.pc' File 'libpcre.pc' appears to be a .pc file Will find package 'libpcre' in file '/usr/lib/pkgconfig/libpcre.pc' File 'neon.pc' appears to be a .pc file Will find package 'neon' in file '/usr/lib/pkgconfig/neon.pc' File 'gkrellm.pc' appears to be a .pc file Will find package 'gkrellm' in file '/usr/lib/pkgconfig/gkrellm.pc' File 'bluez.pc' appears to be a .pc file Will find package 'bluez' in file '/usr/lib/pkgconfig/bluez.pc' File 'libgoom2.pc' appears to be a .pc file Will find package 'libgoom2' in file '/usr/lib/pkgconfig/libgoom2.pc' File 'libwvbase.pc' appears to be a .pc file Will find package 'libwvbase' in file '/usr/lib/pkgconfig/libwvbase.pc' File 'wvxplc.pc' appears to be a .pc file Will find package 'wvxplc' in file '/usr/lib/pkgconfig/wvxplc.pc' File 'ImageMagick++.pc' appears to be a .pc file Will find package 'ImageMagick++' in file '/usr/lib/pkgconfig/ImageMagick++.pc' File 'libwvstreams.pc' appears to be a .pc file Will find package 'libwvstreams' in file '/usr/lib/pkgconfig/libwvstreams.pc' File 'libxml-2.0.pc' appears to be a .pc file Will find package 'libxml-2.0' in file '/usr/lib/pkgconfig/libxml-2.0.pc' File 'mad.pc' appears to be a .pc file Will find package 'mad' in file '/usr/lib/pkgconfig/mad.pc' File 'libcddb.pc' appears to be a .pc file Will find package 'libcddb' in file '/usr/lib/pkgconfig/libcddb.pc' File 'libart-2.0.pc' appears to be a .pc file Will find package 'libart-2.0' in file '/usr/lib/pkgconfig/libart-2.0.pc' File 'libcdio.pc' appears to be a .pc file Will find package 'libcdio' in file '/usr/lib/pkgconfig/libcdio.pc' File 'liboggspeex.pc' appears to be a .pc file Will find package 'liboggspeex' in file '/usr/lib/pkgconfig/liboggspeex.pc' File 'ogg.pc' appears to be a .pc file Will find package 'ogg' in file '/usr/lib/pkgconfig/ogg.pc' File 'nss.pc' appears to be a .pc file Will find package 'nss' in file '/usr/lib/pkgconfig/nss.pc' File 'theora.pc' appears to be a .pc file Will find package 'theora' in file '/usr/lib/pkgconfig/theora.pc' File 'xdamage.pc' appears to be a .pc file Will find package 'xdamage' in file '/usr/lib/pkgconfig/xdamage.pc' File 'id3tag.pc' appears to be a .pc file Will find package 'id3tag' in file '/usr/lib/pkgconfig/id3tag.pc' File 'vorbis.pc' appears to be a .pc file Will find package 'vorbis' in file '/usr/lib/pkgconfig/vorbis.pc' File 'taglib.pc' appears to be a .pc file Will find package 'taglib' in file '/usr/lib/pkgconfig/taglib.pc' File 'resmgr.pc' appears to be a .pc file Will find package 'resmgr' in file '/usr/lib/pkgconfig/resmgr.pc' File 'nspr.pc' appears to be a .pc file Will find package 'nspr' in file '/usr/lib/pkgconfig/nspr.pc' File 'libpng12.pc' appears to be a .pc file Will find package 'libpng12' in file '/usr/lib/pkgconfig/libpng12.pc' File 'zvbi-0.2.pc' appears to be a .pc file Will find package 'zvbi-0.2' in file '/usr/lib/pkgconfig/zvbi-0.2.pc' File 'alsa.pc' appears to be a .pc file Will find package 'alsa' in file '/usr/lib/pkgconfig/alsa.pc' File 'libxine.pc' appears to be a .pc file Will find package 'libxine' in file '/usr/lib/pkgconfig/libxine.pc' File 'xft.pc' appears to be a .pc file Will find package 'xft' in file '/usr/lib/pkgconfig/xft.pc' File 'libexslt.pc' appears to be a .pc file Will find package 'libexslt' in file '/usr/lib/pkgconfig/libexslt.pc' File 'shared-mime-info.pc' appears to be a .pc file Will find package 'shared-mime-info' in file '/usr/lib/pkgconfig/shared-mime-info.pc' File 'uuid.pc' appears to be a .pc file Will find package 'uuid' in file '/usr/lib/pkgconfig/uuid.pc' File 'libwvqt.pc' appears to be a .pc file Will find package 'libwvqt' in file '/usr/lib/pkgconfig/libwvqt.pc' File 'directfb-internal.pc' appears to be a .pc file Will find package 'directfb-internal' in file '/usr/lib/pkgconfig/directfb-internal.pc' File 'com_err.pc' appears to be a .pc file Will find package 'com_err' in file '/usr/lib/pkgconfig/com_err.pc' File 'xevie.pc' appears to be a .pc file Will find package 'xevie' in file '/usr/lib/pkgconfig/xevie.pc' File 'direct.pc' appears to be a .pc file Will find package 'direct' in file '/usr/lib/pkgconfig/direct.pc' File 'libpkcs15init.pc' appears to be a .pc file Will find package 'libpkcs15init' in file '/usr/lib/pkgconfig/libpkcs15init.pc' File 'qt-mt.pc' appears to be a .pc file Will find package 'qt-mt' in file '/usr/lib/pkgconfig/qt-mt.pc' File 'libdv.pc' appears to be a .pc file Will find package 'libdv' in file '/usr/lib/pkgconfig/libdv.pc' File 'libjs.pc' appears to be a .pc file Will find package 'libjs' in file '/usr/lib/pkgconfig/libjs.pc' File 'libvisual.pc' appears to be a .pc file Will find package 'libvisual' in file '/usr/lib/pkgconfig/libvisual.pc' File 'libstartup-notification-1.0.pc' appears to be a .pc file Will find package 'libstartup-notification-1.0' in file '/usr/lib/pkgconfig/libstartup-notification-1.0.pc' File 'libxslt.pc' appears to be a .pc file Will find package 'libxslt' in file '/usr/lib/pkgconfig/libxslt.pc' File 'audiofile.pc' appears to be a .pc file Will find package 'audiofile' in file '/usr/lib/pkgconfig/audiofile.pc' File 'jack.pc' appears to be a .pc file Will find package 'jack' in file '/usr/lib/pkgconfig/jack.pc' File 'gnutls-extra.pc' appears to be a .pc file Will find package 'gnutls-extra' in file '/usr/lib/pkgconfig/gnutls-extra.pc' File 'vorbisfile.pc' appears to be a .pc file Will find package 'vorbisfile' in file '/usr/lib/pkgconfig/vorbisfile.pc' File 'libiso9660.pc' appears to be a .pc file Will find package 'libiso9660' in file '/usr/lib/pkgconfig/libiso9660.pc' File 'libscam.pc' appears to be a .pc file Will find package 'libscam' in file '/usr/lib/pkgconfig/libscam.pc' File 'libopenct.pc' appears to be a .pc file Will find package 'libopenct' in file '/usr/lib/pkgconfig/libopenct.pc' File 'libopensc.pc' appears to be a .pc file Will find package 'libopensc' in file '/usr/lib/pkgconfig/libopensc.pc' File 'wrlib.pc' appears to be a .pc file Will find package 'wrlib' in file '/usr/lib/pkgconfig/wrlib.pc' File 'sndfile.pc' appears to be a .pc file Will find package 'sndfile' in file '/usr/lib/pkgconfig/sndfile.pc' File 'libcdio_paranoia.pc' appears to be a .pc file Will find package 'libcdio_paranoia' in file '/usr/lib/pkgconfig/libcdio_paranoia.pc' File 'limal.pc' appears to be a .pc file Will find package 'limal' in file '/usr/lib/pkgconfig/limal.pc' File 'fontconfig.pc' appears to be a .pc file Will find package 'fontconfig' in file '/usr/lib/pkgconfig/fontconfig.pc' File 'directfb.pc' appears to be a .pc file Will find package 'directfb' in file '/usr/lib/pkgconfig/directfb.pc' File 'glitz-glx.pc' appears to be a .pc file Will find package 'glitz-glx' in file '/usr/lib/pkgconfig/glitz-glx.pc' File 'blocxx.pc' appears to be a .pc file Will find package 'blocxx' in file '/usr/lib/pkgconfig/blocxx.pc' Scanning directory '/usr/share/pkgconfig' Ignoring file '.' in search directory; not a .pc file Ignoring file '..' in search directory; not a .pc file Looking for package 'exiv2' Looking for package 'exiv2-uninstalled' Reading 'exiv2' from file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' Parsing package file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' line>prefix=/home/digi/digikamSVN/ Variable declaration, 'prefix' has value '/home/digi/digikamSVN/' line>exec_prefix=${prefix} Variable declaration, 'exec_prefix' has value '/home/digi/digikamSVN/' line>libdir=${exec_prefix}/lib Variable declaration, 'libdir' has value '/home/digi/digikamSVN//lib' line>includedir=${prefix}/include Variable declaration, 'includedir' has value '/home/digi/digikamSVN//include' line> line>Name: exiv2 line>Description: Exif and IPTC metadata library and tools line>Version: 0.12 line>URL: http://www.exiv2.org line>Libs: -L${libdir} -lexiv2 line>Libs.private: -lz -lm line>Cflags: -I${includedir} Path position of 'exiv2' is 1 Adding 'exiv2' to list of known packages, returning as package 'exiv2' digi@venus:~> > ... > > Could you also put the graphics/config.log file in your website ? > here it is: http://www.daniel-bauer.com/test/config.log.txt Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Daniel Bauer wrote:
> On Tuesday 05 December 2006 15:26, Fabien wrote: > >>Can you try to run : >>pkg-config --debug --exists "exiv2 >= 0.12" >> >>after using the exports in your shell ? > > > Did you mean typing the export commands from the complie_digikam.sh script and > then the above? If so, here's what I get: > > digi@venus:~> export DIGIKAMDEST=/home/digi/digikamSVN/ > digi@venus:~> export KDEDIRS=$DIGIKAMDEST:/usr ; export > LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export > LDPATH=$DIGIKAMDEST/lib:$LDPATH > digi@venus:~> export UNSERMAKE=no > digi@venus:~> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig > digi@venus:~> export PATH=$DIGIKAMDEST/bin:$PATH > digi@venus:~> pkg-config --debug --exists "exiv2 >= 0.12" > [...] > Looking for package 'exiv2' > Looking for package 'exiv2-uninstalled' > Reading 'exiv2' from file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > Parsing package file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > line>prefix=/home/digi/digikamSVN/ > Variable declaration, 'prefix' has value '/home/digi/digikamSVN/' > line>exec_prefix=${prefix} > Variable declaration, 'exec_prefix' has value '/home/digi/digikamSVN/' > line>libdir=${exec_prefix}/lib > Variable declaration, 'libdir' has value '/home/digi/digikamSVN//lib' > line>includedir=${prefix}/include > Variable declaration, 'includedir' has value '/home/digi/digikamSVN//include' > line> > line>Name: exiv2 > line>Description: Exif and IPTC metadata library and tools > line>Version: 0.12 > line>URL: http://www.exiv2.org > line>Libs: -L${libdir} -lexiv2 > line>Libs.private: -lz -lm > line>Cflags: -I${includedir} > Path position of 'exiv2' is 1 > Adding 'exiv2' to list of known packages, returning as package 'exiv2' > digi@venus:~> Well, everything looks good... >>Could you also put the graphics/config.log file in your website ? > > here it is: > > http://www.daniel-bauer.com/test/config.log.txt Really weird... Just to be sure, can you run : sh --version -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 05 December 2006 17:44, Fabien wrote:
> Daniel Bauer wrote: > > On Tuesday 05 December 2006 15:26, Fabien wrote: > >>Can you try to run : > >>pkg-config --debug --exists "exiv2 >= 0.12" > >> > >>after using the exports in your shell ? > > > > Did you mean typing the export commands from the complie_digikam.sh > > script and then the above? If so, here's what I get: > > > > digi@venus:~> export DIGIKAMDEST=/home/digi/digikamSVN/ > > digi@venus:~> export KDEDIRS=$DIGIKAMDEST:/usr ; export > > LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export > > LDPATH=$DIGIKAMDEST/lib:$LDPATH > > digi@venus:~> export UNSERMAKE=no > > digi@venus:~> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig > > digi@venus:~> export PATH=$DIGIKAMDEST/bin:$PATH > > digi@venus:~> pkg-config --debug --exists "exiv2 >= 0.12" > > > > [...] > > > > Looking for package 'exiv2' > > Looking for package 'exiv2-uninstalled' > > Reading 'exiv2' from file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > > Parsing package file '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > > line>prefix=/home/digi/digikamSVN/ > > Variable declaration, 'prefix' has value '/home/digi/digikamSVN/' > > line>exec_prefix=${prefix} > > Variable declaration, 'exec_prefix' has value '/home/digi/digikamSVN/' > > line>libdir=${exec_prefix}/lib > > Variable declaration, 'libdir' has value '/home/digi/digikamSVN//lib' > > line>includedir=${prefix}/include > > Variable declaration, 'includedir' has value > > '/home/digi/digikamSVN//include' line> > > line>Name: exiv2 > > line>Description: Exif and IPTC metadata library and tools > > line>Version: 0.12 > > line>URL: http://www.exiv2.org > > line>Libs: -L${libdir} -lexiv2 > > line>Libs.private: -lz -lm > > line>Cflags: -I${includedir} > > Path position of 'exiv2' is 1 > > Adding 'exiv2' to list of known packages, returning as package 'exiv2' > > digi@venus:~> > > Well, everything looks good... > > >>Could you also put the graphics/config.log file in your website ? > > > > here it is: > > > > http://www.daniel-bauer.com/test/config.log.txt > > Really weird... Yes, maybe my computer aligns with me ;-) > Just to be sure, can you run : > sh --version : GNU bash, version 3.00.16(1)-release (i586-suse-linux) Copyright (C) 2004 Free Software Foundation, Inc. --- There must have been a change when it changed to the 0.12 version. I have done several svn up and compiles before that, never had any problems. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Am Dienstag 05 Dezember 2006 17:57 schrieb Daniel Bauer:
> On Tuesday 05 December 2006 17:44, Fabien wrote: > > Daniel Bauer wrote: > > > On Tuesday 05 December 2006 15:26, Fabien wrote: > > >>Can you try to run : > > >>pkg-config --debug --exists "exiv2 >= 0.12" > > >> > > >>after using the exports in your shell ? > > > > > > Did you mean typing the export commands from the complie_digikam.sh > > > script and then the above? If so, here's what I get: > > > > > > digi@venus:~> export DIGIKAMDEST=/home/digi/digikamSVN/ > > > digi@venus:~> export KDEDIRS=$DIGIKAMDEST:/usr ; export > > > LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export > > > LDPATH=$DIGIKAMDEST/lib:$LDPATH > > > digi@venus:~> export UNSERMAKE=no > > > digi@venus:~> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig > > > digi@venus:~> export PATH=$DIGIKAMDEST/bin:$PATH > > > digi@venus:~> pkg-config --debug --exists "exiv2 >= 0.12" > > > > > > [...] > > > > > > Looking for package 'exiv2' > > > Looking for package 'exiv2-uninstalled' > > > Reading 'exiv2' from file > > > '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' Parsing package file > > > '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > > > line>prefix=/home/digi/digikamSVN/ > > > Variable declaration, 'prefix' has value '/home/digi/digikamSVN/' > > > line>exec_prefix=${prefix} > > > Variable declaration, 'exec_prefix' has value '/home/digi/digikamSVN/' > > > line>libdir=${exec_prefix}/lib > > > Variable declaration, 'libdir' has value '/home/digi/digikamSVN//lib' > > > line>includedir=${prefix}/include > > > Variable declaration, 'includedir' has value > > > '/home/digi/digikamSVN//include' line> > > > line>Name: exiv2 > > > line>Description: Exif and IPTC metadata library and tools > > > line>Version: 0.12 > > > line>URL: http://www.exiv2.org > > > line>Libs: -L${libdir} -lexiv2 > > > line>Libs.private: -lz -lm > > > line>Cflags: -I${includedir} > > > Path position of 'exiv2' is 1 > > > Adding 'exiv2' to list of known packages, returning as package 'exiv2' > > > digi@venus:~> > > > > Well, everything looks good... > > > > >>Could you also put the graphics/config.log file in your website ? > > > > > > here it is: > > > > > > http://www.daniel-bauer.com/test/config.log.txt > > > > Really weird... > > Yes, maybe my computer aligns with me ;-) > > > Just to be sure, can you run : > > sh --version > > GNU bash, version 3.00.16(1)-release (i586-suse-linux) > Copyright (C) 2004 Free Software Foundation, Inc. > > --- > There must have been a change when it changed to the 0.12 version. I have > done several svn up and compiles before that, never had any problems. > > Daniel Hi Daniel, configure:36274: checking for exiv2-config configure:36292: found /home/digi/digikamSVN//bin/exiv2-config configure:36304: result: /home/digi/digikamSVN//bin/exiv2-config configure:36370: checking for exiv2 >= 0.12 configure:36416: result: no configure:36419: WARNING: Exiv2 library not found, digiKam will not be compiled. Is it right that /home/digi/digikamSVN//bin/exiv2-config is the correct version? /home/digi/digikamSVN//bin/exiv2-config --version tells you what? can you put "configure" also on your webspace? The error is between the lines 36370...36416 of this script. Bye Thorsten _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
Daniel Bauer wrote:
> On Tuesday 05 December 2006 17:44, Fabien wrote: >>>>Could you also put the graphics/config.log file in your website ? >>> >>>here it is: >>> >>>http://www.daniel-bauer.com/test/config.log.txt >> >>Really weird... > > > Yes, maybe my computer aligns with me ;-) > > >>Just to be sure, can you run : >>sh --version > > : > GNU bash, version 3.00.16(1)-release (i586-suse-linux) > Copyright (C) 2004 Free Software Foundation, Inc. Ok, that's fine. > --- > There must have been a change when it changed to the 0.12 version. I have done > several svn up and compiles before that, never had any problems. Yes, there was a change to require exiv2 >= 0.12 Let's try again something : Could you clean up everything again, and run again the scripts without the trailing / at the end of the path ? Then, put all the results in your website, + the scripts, + graphics/config.log and graphics/configure And let everything like that. If the problem still persists, I will give you an updated configure script to add some debug... -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Bugzilla from thorsten.schnebeck@gmx.net
On Tuesday 05 December 2006 18:20, Thorsten Schnebeck wrote:
> Am Dienstag 05 Dezember 2006 17:57 schrieb Daniel Bauer: > > On Tuesday 05 December 2006 17:44, Fabien wrote: > > > Daniel Bauer wrote: > > > > On Tuesday 05 December 2006 15:26, Fabien wrote: > > > >>Can you try to run : > > > >>pkg-config --debug --exists "exiv2 >= 0.12" > > > >> > > > >>after using the exports in your shell ? > > > > > > > > Did you mean typing the export commands from the complie_digikam.sh > > > > script and then the above? If so, here's what I get: > > > > > > > > digi@venus:~> export DIGIKAMDEST=/home/digi/digikamSVN/ > > > > digi@venus:~> export KDEDIRS=$DIGIKAMDEST:/usr ; export > > > > LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ; export > > > > LDPATH=$DIGIKAMDEST/lib:$LDPATH > > > > digi@venus:~> export UNSERMAKE=no > > > > digi@venus:~> export PKG_CONFIG_PATH=$DIGIKAMDEST/lib/pkgconfig > > > > digi@venus:~> export PATH=$DIGIKAMDEST/bin:$PATH > > > > digi@venus:~> pkg-config --debug --exists "exiv2 >= 0.12" > > > > > > > > [...] > > > > > > > > Looking for package 'exiv2' > > > > Looking for package 'exiv2-uninstalled' > > > > Reading 'exiv2' from file > > > > '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' Parsing package file > > > > '/home/digi/digikamSVN//lib/pkgconfig/exiv2.pc' > > > > line>prefix=/home/digi/digikamSVN/ > > > > Variable declaration, 'prefix' has value '/home/digi/digikamSVN/' > > > > line>exec_prefix=${prefix} > > > > Variable declaration, 'exec_prefix' has value > > > > '/home/digi/digikamSVN/' line>libdir=${exec_prefix}/lib > > > > Variable declaration, 'libdir' has value > > > > '/home/digi/digikamSVN//lib' line>includedir=${prefix}/include > > > > Variable declaration, 'includedir' has value > > > > '/home/digi/digikamSVN//include' line> > > > > line>Name: exiv2 > > > > line>Description: Exif and IPTC metadata library and tools > > > > line>Version: 0.12 > > > > line>URL: http://www.exiv2.org > > > > line>Libs: -L${libdir} -lexiv2 > > > > line>Libs.private: -lz -lm > > > > line>Cflags: -I${includedir} > > > > Path position of 'exiv2' is 1 > > > > Adding 'exiv2' to list of known packages, returning as package > > > > 'exiv2' digi@venus:~> > > > > > > Well, everything looks good... > > > > > > >>Could you also put the graphics/config.log file in your website ? > > > > > > > > here it is: > > > > > > > > http://www.daniel-bauer.com/test/config.log.txt > > > > > > Really weird... > > > > Yes, maybe my computer aligns with me ;-) > > > > > Just to be sure, can you run : > > > sh --version > > > > GNU bash, version 3.00.16(1)-release (i586-suse-linux) > > Copyright (C) 2004 Free Software Foundation, Inc. > > > > --- > > There must have been a change when it changed to the 0.12 version. I have > > done several svn up and compiles before that, never had any problems. > > > > Daniel > > Hi Daniel, Hi Thorsten > configure:36274: checking for exiv2-config > configure:36292: found /home/digi/digikamSVN//bin/exiv2-config > configure:36304: result: /home/digi/digikamSVN//bin/exiv2-config > configure:36370: checking for exiv2 >= 0.12 > configure:36416: result: no > configure:36419: WARNING: Exiv2 library not found, digiKam will not be > compiled. > > Is it right that > /home/digi/digikamSVN//bin/exiv2-config > is the correct version? I guess, at least the executable file exiv2 is there... > > /home/digi/digikamSVN//bin/exiv2-config --version > tells you what? 0.11 !!! (without the !!!) how comes? > can you put "configure" also on your webspace? /home/digi/digikam_svn/graphics/configure ? it's here: http://www.daniel-bauer.com/test/configure.txt (1.3 MB) I'll now start the next try and replace the files in an hour or two with the next versions unless it works... regards Daniel > > The error is between the lines 36370...36416 of this script. > > Bye > > Thorsten -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Fabien-5
On Tuesday 05 December 2006 18:21, Fabien wrote:
> Daniel Bauer wrote: > > On Tuesday 05 December 2006 17:44, Fabien wrote: > >>>>Could you also put the graphics/config.log file in your website ? > >>> > >>>here it is: > >>> > >>>http://www.daniel-bauer.com/test/config.log.txt > >> > >>Really weird... > > > > Yes, maybe my computer aligns with me ;-) > > > >>Just to be sure, can you run : > >>sh --version > > > > GNU bash, version 3.00.16(1)-release (i586-suse-linux) > > Copyright (C) 2004 Free Software Foundation, Inc. > > Ok, that's fine. > > > --- > > There must have been a change when it changed to the 0.12 version. I have > > done several svn up and compiles before that, never had any problems. > > Yes, there was a change to require exiv2 >= 0.12 > > Let's try again something : > Could you clean up everything again, and run again the scripts without > the trailing / at the end of the path ? > > Then, put all the results in your website, + the scripts, + > graphics/config.log and graphics/configure > > And let everything like that. If the problem still persists, I will give > you an updated configure script to add some debug... > > -- > Fabien ok, I'll mail when I'm finished. Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Daniel Bauer-2
> > Is it right that
> > /home/digi/digikamSVN//bin/exiv2-config > > is the correct version? > > I guess, at least the executable file exiv2 is there... > > > /home/digi/digikamSVN//bin/exiv2-config --version > > tells you what? > > 0.11 !!! (without the !!!) > how comes? So, I took you script and used that to update my own exiv2-package. That works without problems. So you _must_ have an old version? I checked the SVN trunk - there is no error in versioning. Did you miss a "make install"? try a cd exiv2-svn make uninstall cd .. rm -r exiv2-svn and start your exiv2 build script again HTH Thorsten _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by Fabien-5
On Tuesday 05 December 2006 18:21, Fabien wrote:
> Let's try again something : > Could you clean up everything again, and run again the scripts without > the trailing / at the end of the path ? > > Then, put all the results in your website, + the scripts, + > graphics/config.log and graphics/configure > > And let everything like that. If the problem still persists, I will give > you an updated configure script to add some debug... > here are the new files: http://www.daniel-bauer.com/test/compile_digikam.out.txt http://www.daniel-bauer.com/test/compile_exiv2.out.txt http://www.daniel-bauer.com/test/config.log.txt http://www.daniel-bauer.com/test/configure.txt http://www.daniel-bauer.com/test/compile_digikam.sh.txt http://www.daniel-bauer.com/test/compile_exiv2.sh.txt sorry to cause so much work to you... Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com Madagascar special: http://www.sanic.ch _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |