"Install digiKam in your Home Directory" wouldn't work :-(

[Daniel Bauer-2]

Hi everybody

After a long time with no time for experiments (always working with 0.8.2 and
sometimes with a old svn-version from 2.6.2006...) I found the scripts on
your website (http://www.digikam.org/?q=download/svn)  to install the svn
version in a separate directory.

But the digikam-compile ends with errors:

ERROR:kipi-plugins/printwizard/Makefile.am: unknown source extension .ui for
kipiplugin_printwizard.la
ERROR:kipi-plugins/batchprocessimages/Makefile.am: unknown source
extension .ui for kipiplugin_batchprocessimages.la
ERROR:kipi-plugins/galleryexport/Makefile.am: unknown source extension .ui for
kipiplugin_galleryexport.la
ERROR:kipi-plugins/flickrexport/Makefile.am: unknown source extension .ui for
kipiplugin_flickrexport.la
ERROR:kipi-plugins/slideshow/Makefile.am: unknown source extension .ui for
kipiplugin_slideshow.la
ERROR:kipi-plugins/htmlexport/Makefile.am: unknown source extension .ui for
kipiplugin_htmlexport.la
ERROR:kipi-plugins/htmlexport/Makefile.am: unknown source extension .ui for
kipiplugin_htmlexport.la
ERROR:kipi-plugins/htmlexport/Makefile.am: unknown source extension .ui for
kipiplugin_htmlexport.la
ERROR:kipi-plugins/htmlexport/Makefile.am: unknown source extension .kcfgc for
kipiplugin_htmlexport.la
make: *** [all] Fehler 1


What did I do wrong?
Do I have to change some other settings/prefeixes...? (I am working on
OpenSuse 10.0, KDE 3.5.4)

Can you help me a step forward?
Thanks.

Daniel

-------------------
If you want to look at the complete compiler-output you can see it here:
http://www.daniel-bauer.com/test/exiv2.txt
http://www.daniel-bauer.com/test/digikam.txt

Here's what I did:
- made a directory /home/test/digikam_svn
- and another directory /home/test/digikamSVN
- downloaded "compile_exiv2.sh" and "compile_digikam.sh" and put them
in /home/test/digikam_svn
- downloaded "start_digikam.sh" and put it on Desktop
- adjusted DIGIKAMDEST to /home/test/digikamSVN in all 3 scripts
- cd to /home/test/digikam_svn
- run ./compile_exiv2.sh, then ./compile_digikam.sh
???





--
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

[Fabien-5]

Hi,

Daniel Bauer wrote:

> After a long time with no time for experiments (always working with 0.8.2 and
> sometimes with a old svn-version from 2.6.2006...) I found the scripts on
> your website (http://www.digikam.org/?q=download/svn)  to install the svn
> version in a separate directory.
>
> But the digikam-compile ends with errors:
>
>
> What did I do wrong?
> Do I have to change some other settings/prefeixes...? (I am working on
> OpenSuse 10.0, KDE 3.5.4)

Hmm, I think it's relevant to unsermake.
There are some warnings in log about that.
Try to use gnu make instead (gmake).

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

Hi, (sorry for braking the thread. I received only part of the emails from the
list yet and found your answer in the online archive...)

Fabien write:
> Hi,

> Daniel Bauer wrote:
>> After a long time with no time for experiments (always working with 0.8.2 >
>> and
>> sometimes with a old svn-version from 2.6.2006...) I found the scripts on
>> your website (http://www.digikam.org/?q=download/svn)  to install the svn
>> version in a separate directory.
>>
>> But the digikam-compile ends with errors:
>>
>>
>> What did I do wrong?
>> Do I have to change some other settings/prefeixes...? (I am working on
>> OpenSuse 10.0, KDE 3.5.4)

>Hmm, I think it's relevant to unsermake.
>There are some warnings in log about that.
>Try to use gnu make instead (gmake).

> Fabien

Do you mean simply replacing all "make" by "gmake" in "compile_digikam.sh"?
I tried that, but it leads to the same errors.

I just doublechecked: I have installed both unsermake and GNU make. I'm not
sure, but I guess on my system "make" is similar to "gmake". So I gave it
another try replacing all 8 "make" in the script by "unsermake" (including
those in "make install") .

Now the process went further, but then stopped after compiling/linking
kipi-plugins with:

/usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld: cannot
find -lkipiplugins
collect2: ld returned 1 exit status
Error creating ./kipi-plugins/mpegencoder/kipiplugin_mpegencoder.la. Exit
status 1.

the complete output is here:
http://www.daniel-bauer.com/test/digikamunsermake.txt

What else can I try?

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

[Fabien-5]

Daniel Bauer wrote:
> Hi, (sorry for braking the thread. I received only part of the emails from the
> list yet and found your answer in the online archive...)

Ok, so I CC to you :)

>>Daniel Bauer wrote:
>>
  >>Hmm, I think it's relevant to unsermake.
>>There are some warnings in log about that.
>>Try to use gnu make instead (gmake).
>
> Do you mean simply replacing all "make" by "gmake" in "compile_digikam.sh"?
> I tried that, but it leads to the same errors.

That's weird...

> I just doublechecked: I have installed both unsermake and GNU make. I'm not
> sure, but I guess on my system "make" is similar to "gmake". So I gave it
> another try replacing all 8 "make" in the script by "unsermake" (including
> those in "make install") .
>
> Now the process went further, but then stopped after compiling/linking
> kipi-plugins with:
>
> /usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld: cannot
> find -lkipiplugins
> collect2: ld returned 1 exit status
> Error creating ./kipi-plugins/mpegencoder/kipiplugin_mpegencoder.la. Exit
> status 1.
>
> the complete output is here:
> http://www.daniel-bauer.com/test/digikamunsermake.txt
>
> What else can I try?

Could you try to uninstall unsermake and to use only gnu make ?
You should also remove all the directories/files created by the scripts
to be sure you compile from clean checkout.
You should not see theses warning about unsermake...

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

Le Mardi 14 Novembre 2006 17:06, Daniel Bauer a écrit :

> Hi, (sorry for braking the thread. I received only part of the emails from
> the list yet and found your answer in the online archive...)
>
> Fabien write:
> > Hi,
> >
> > Daniel Bauer wrote:
> >> After a long time with no time for experiments (always working with
> >> 0.8.2 > and
> >> sometimes with a old svn-version from 2.6.2006...) I found the scripts
> >> on your website (http://www.digikam.org/?q=download/svn)  to install the
> >> svn version in a separate directory.
> >>
> >> But the digikam-compile ends with errors:
> >>
> >>
> >> What did I do wrong?
> >> Do I have to change some other settings/prefeixes...? (I am working on
> >> OpenSuse 10.0, KDE 3.5.4)
> >
> >Hmm, I think it's relevant to unsermake.
> >There are some warnings in log about that.
> >Try to use gnu make instead (gmake).
> >
> > Fabien
>
> Do you mean simply replacing all "make" by "gmake" in "compile_digikam.sh"?
> I tried that, but it leads to the same errors.
>
> I just doublechecked: I have installed both unsermake and GNU make. I'm not
> sure, but I guess on my system "make" is similar to "gmake". So I gave it
> another try replacing all 8 "make" in the script by "unsermake" (including
> those in "make install") .
>
> Now the process went further, but then stopped after compiling/linking
> kipi-plugins with:
>
> /usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
> cannot find -lkipiplugins
> collect2: ld returned 1 exit status
> Error creating ./kipi-plugins/mpegencoder/kipiplugin_mpegencoder.la. Exit
> status 1.
>
> the complete output is here:
> http://www.daniel-bauer.com/test/digikamunsermake.txt
>
> What else can I try?
>
> Daniel

Hi Daniel. I'm happy to see in this room (:=))

The problem is to use automake program (from GNU autotools package) instead
unsermake (witch is not supported by digiKam team).

automake is an old program, a mittle bit complicated to manage but very
powerfull. unsermake have been developped by KDE team to remplace automake,
but, it's not finalized and can break compilation. We have no time to debug
another BUILD tools, and we want to support the standard way diffused on all
linux box.

Also, in the future (KDE4), the new tool CMake will be used. it's a powerfull
remplacant of automake. This is why i won't lost some time with unsermake.
When digikam and co will be ported to Qt4/KDE4, CMake will be used instead
automake.

Here, on my computers (2 at home, 15 in my office), i'm trying to compile
digiKam and co under a lots of linux box (Mandriva 2005/2006/2007, Suse 10.1,
Kubuntu) and all use automake.

Friendly

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Tuesday 14 November 2006 18:30, Caulier Gilles wrote:

> Le Mardi 14 Novembre 2006 17:06, Daniel Bauer a écrit :
> > Hi, (sorry for braking the thread. I received only part of the emails
> > from the list yet and found your answer in the online archive...)
> >
> > Fabien write:
> > > Hi,
> > >
> > > Daniel Bauer wrote:
> > >> After a long time with no time for experiments (always working with
> > >> 0.8.2 > and
> > >> sometimes with a old svn-version from 2.6.2006...) I found the scripts
> > >> on your website (http://www.digikam.org/?q=download/svn)  to install
> > >> the svn version in a separate directory.
> > >>
> > >> But the digikam-compile ends with errors:
> > >>
> > >>
> > >> What did I do wrong?
> > >> Do I have to change some other settings/prefeixes...? (I am working on
> > >> OpenSuse 10.0, KDE 3.5.4)
> > >
> > >Hmm, I think it's relevant to unsermake.
> > >There are some warnings in log about that.
> > >Try to use gnu make instead (gmake).
> > >
> > > Fabien
> >
> > Do you mean simply replacing all "make" by "gmake" in
> > "compile_digikam.sh"? I tried that, but it leads to the same errors.
> >
> > I just doublechecked: I have installed both unsermake and GNU make. I'm
> > not sure, but I guess on my system "make" is similar to "gmake". So I
> > gave it another try replacing all 8 "make" in the script by "unsermake"
> > (including those in "make install") .
> >
> > Now the process went further, but then stopped after compiling/linking
> > kipi-plugins with:
> >
> > /usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
> > cannot find -lkipiplugins
> > collect2: ld returned 1 exit status
> > Error creating ./kipi-plugins/mpegencoder/kipiplugin_mpegencoder.la. Exit
> > status 1.
> >
> > the complete output is here:
> > http://www.daniel-bauer.com/test/digikamunsermake.txt
> >
> > What else can I try?
> >
> > Daniel
>
> Hi Daniel. I'm happy to see in this room (:=))
>
> The problem is to use automake program (from GNU autotools package) instead
> unsermake (witch is not supported by digiKam team).
>
> automake is an old program, a mittle bit complicated to manage but very
> powerfull. unsermake have been developped by KDE team to remplace automake,
> but, it's not finalized and can break compilation. We have no time to debug
> another BUILD tools, and we want to support the standard way diffused on
> all linux box.
>
> Also, in the future (KDE4), the new tool CMake will be used. it's a
> powerfull remplacant of automake. This is why i won't lost some time with
> unsermake. When digikam and co will be ported to Qt4/KDE4, CMake will be
> used instead automake.
>
> Here, on my computers (2 at home, 15 in my office), i'm trying to compile
> digiKam and co under a lots of linux box (Mandriva 2005/2006/2007, Suse
> 10.1, Kubuntu) and all use automake.
>
> Friendly
>
> Gilles

Hi Gilles, hi Fabien

Since Fabien told me to uninstall unsermake, and after your explenations
above, I finally decided to unistall it and check "risk an unstable
system"...

And, guess what: the compile run successfully!

So, Fabien was right.  For Suse-Users it seems to be important that unsermake
is *not* installed when compiling digikam. (I will see tomorrow if my PC
still boots and runs correctly, but as far as I saw in the conflicts list,
only kde-devel packages are affected - at least, thats what I hope :-) )

Right now digikam is crashing immediately after showing the splash screen
animal - but thats another story and I'm going to read thru the mailing list
mails tomorrow before asking further questions here ;-)

Thanks for the support!

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

[Gilles Caulier-2]

Le Mardi 14 Novembre 2006 21:11, Daniel Bauer a écrit :

> On Tuesday 14 November 2006 18:30, Caulier Gilles wrote:
> > Le Mardi 14 Novembre 2006 17:06, Daniel Bauer a écrit :
> > > Hi, (sorry for braking the thread. I received only part of the emails
> > > from the list yet and found your answer in the online archive...)
> > >
> > > Fabien write:
> > > > Hi,
> > > >
> > > > Daniel Bauer wrote:
> > > >> After a long time with no time for experiments (always working with
> > > >> 0.8.2 > and
> > > >> sometimes with a old svn-version from 2.6.2006...) I found the
> > > >> scripts on your website (http://www.digikam.org/?q=download/svn)  to
> > > >> install the svn version in a separate directory.
> > > >>
> > > >> But the digikam-compile ends with errors:
> > > >>
> > > >>
> > > >> What did I do wrong?
> > > >> Do I have to change some other settings/prefeixes...? (I am working
> > > >> on OpenSuse 10.0, KDE 3.5.4)
> > > >
> > > >Hmm, I think it's relevant to unsermake.
> > > >There are some warnings in log about that.
> > > >Try to use gnu make instead (gmake).
> > > >
> > > > Fabien
> > >
> > > Do you mean simply replacing all "make" by "gmake" in
> > > "compile_digikam.sh"? I tried that, but it leads to the same errors.
> > >
> > > I just doublechecked: I have installed both unsermake and GNU make. I'm
> > > not sure, but I guess on my system "make" is similar to "gmake". So I
> > > gave it another try replacing all 8 "make" in the script by "unsermake"
> > > (including those in "make install") .
> > >
> > > Now the process went further, but then stopped after compiling/linking
> > > kipi-plugins with:
> > >
> > > /usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/bin/ld:
> > > cannot find -lkipiplugins
> > > collect2: ld returned 1 exit status
> > > Error creating ./kipi-plugins/mpegencoder/kipiplugin_mpegencoder.la.
> > > Exit status 1.
> > >
> > > the complete output is here:
> > > http://www.daniel-bauer.com/test/digikamunsermake.txt
> > >
> > > What else can I try?
> > >
> > > Daniel
> >
> > Hi Daniel. I'm happy to see in this room (:=))
> >
> > The problem is to use automake program (from GNU autotools package)
> > instead unsermake (witch is not supported by digiKam team).
> >
> > automake is an old program, a mittle bit complicated to manage but very
> > powerfull. unsermake have been developped by KDE team to remplace
> > automake, but, it's not finalized and can break compilation. We have no
> > time to debug another BUILD tools, and we want to support the standard
> > way diffused on all linux box.
> >
> > Also, in the future (KDE4), the new tool CMake will be used. it's a
> > powerfull remplacant of automake. This is why i won't lost some time with
> > unsermake. When digikam and co will be ported to Qt4/KDE4, CMake will be
> > used instead automake.
> >
> > Here, on my computers (2 at home, 15 in my office), i'm trying to compile
> > digiKam and co under a lots of linux box (Mandriva 2005/2006/2007, Suse
> > 10.1, Kubuntu) and all use automake.
> >
> > Friendly
> >
> > Gilles
>
> Hi Gilles, hi Fabien
>
> Since Fabien told me to uninstall unsermake, and after your explenations
> above, I finally decided to unistall it and check "risk an unstable
> system"...
>
> And, guess what: the compile run successfully!
>
> So, Fabien was right.  For Suse-Users it seems to be important that
> unsermake is *not* installed when compiling digikam. (I will see tomorrow
> if my PC still boots and runs correctly, but as far as I saw in the
> conflicts list, only kde-devel packages are affected - at least, thats what
> I hope :-) )
>
> Right now digikam is crashing immediately after showing the splash screen
> animal - but thats another story and I'm going to read thru the mailing
> list mails tomorrow before asking further questions here ;-)

Sound linke these files :

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

This is certainly another crash releavant of Exiv2 bug. I'm working on.

To confirm it, if you can give me a GDB trace like it's explained here :

http://www.digikam.org/?q=contrib

Thanks in advance

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Tuesday 14 November 2006 21:38, Caulier Gilles wrote:
> Le Mardi 14 Novembre 2006 21:11, Daniel Bauer a écrit :

> > Right now digikam is crashing immediately after showing the splash screen
> > animal - but thats another story and I'm going to read thru the mailing
> > list mails tomorrow before asking further questions here ;-)
>
> Sound linke these files :
>
> 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
>
> This is certainly another crash releavant of Exiv2 bug. I'm working on.
>
> To confirm it, if you can give me a GDB trace like it's explained here :
>
> http://www.digikam.org/?q=contrib
>
> Thanks in advance
>
> Gilles

Good Morning Gilles,

So I hope I did it right - here's what I got from gdb:

 (gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x41d44541 in raise () from /lib/tls/libc.so.6
#2  0x41d45dbb in abort () from /lib/tls/libc.so.6
#3  0x41cc2489 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#4  0x41cbfe15 in __gxx_personality_v0 () from /usr/lib/libstdc++.so.6
#5  0x41cbfe52 in std::terminate () from /usr/lib/libstdc++.so.6
#6  0x41cbffba in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x40680c41 in Exiv2::ExifTags::registerMakerTagInfo (
    ifdId=Exiv2::ifdIdNotSet, tagInfo=0x6) at tags.cpp:1137
#8  0x40679b04 in RegisterMn (this=0x431924a8) at sigmamn.cpp:59
#9  0x4314c2a3 in __static_initialization_and_destruction_0 (
    __initialize_p=<value optimized out>, __priority=<value optimized out>)
    at sigmamn.hpp:148
#10 0x43165dc6 in __do_global_ctors_aux ()
from /usr/local/lib/libexiv2-0.10.so
#11 0x43101425 in _init () from /usr/local/lib/libexiv2-0.10.so
#12 0x4000b9a4 in call_init () from /lib/ld-linux.so.2
#13 0x4000bae1 in _dl_init_internal () from /lib/ld-linux.so.2
#14 0x41e0ded1 in dl_open_worker () from /lib/tls/libc.so.6
#15 0x4000b82f in _dl_catch_error () from /lib/ld-linux.so.2
#16 0x41e0e546 in _dl_open () from /lib/tls/libc.so.6
#17 0x41c0cd68 in dlopen_doit () from /lib/libdl.so.2
#18 0x4000b82f in _dl_catch_error () from /lib/ld-linux.so.2
#19 0x41c0d37e in _dlerror_run () from /lib/libdl.so.2
#20 0x41c0cdc1 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2
#21 0x410ead31 in sys_dl_open () from /opt/kde3/lib/libkdecore.so.4
#22 0x410eb610 in tryall_dlopen () from /opt/kde3/lib/libkdecore.so.4
#23 0x410ed235 in lt_dlopen () from /opt/kde3/lib/libkdecore.so.4
#24 0x410310b6 in KLibLoader::library () from /opt/kde3/lib/libkdecore.so.4
#25 0x40584f8d in KIPI::PluginLoader::loadPlugin ()
   from /home/digi/digikamSVN//lib/libkipi.so.0
#26 0x40585b6f in KIPI::PluginLoader::loadPlugins ()
   from /home/digi/digikamSVN//lib/libkipi.so.0
#27 0x4015f440 in Digikam::DigikamApp::loadPlugins (this=0x817bea8)
    at digikamapp.cpp:1497
#28 0x40164ca6 in DigikamApp (this=0x817bea8) at digikamapp.cpp:170
#29 0x0804a713 in main (argc=1, argv=0xbf946f34) at main.cpp:244

For me this is all just cryptic, could be chinese, too :-)

I just wonder about the /usr/local/lib/libexiv2-0.10.so lines, because my svn
compiled versions are here: /home/digi/digikamSVN/lib

Do I need another prefix or something for configure?

This is what I've done this morning:

        cd /home/digi/digikam_svn/exiv2-svn
        svn up
        sudo make uninstall
        make config
        ./configure --prefix=/home/digi/digikamSVN/
        make
        make install

        cd /home/digi/digikam_svn/graphics
        svn up digikam
        svn up digikamimageplugins
        sudo make distclean
        make -f Makefile.cvs
        ./configure -prefix=/home/digi/digikamSVN/ --with-extra-includes=/home/digi/digikamSVN/include --with-extra-libs=/home/digi/digikamSVN/lib --enable-debug=full
        make
        make install

kind regards

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

[Fabien-5]

Daniel Bauer wrote:
> I just wonder about the /usr/local/lib/libexiv2-0.10.so lines, because my svn
> compiled versions are here: /home/digi/digikamSVN/lib

Yes, that's a problem.

> Do I need another prefix or something for configure?
>
> This is what I've done this morning:
>
 > [...]

It looks ok. More important, I think, is how you start digikam.
Try to see lib dependencies with ldd :
# ldd digikam | grep -i exiv2

It's important to use the environment variables, eg :
# export DIGIKAMDEST=/opt/digikam
# export KDEDIRS=$DIGIKAMDEST:/usr
# export LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH
# export PATH=$DIGIKAMDEST/bin:$PATH

before starting digikam (also with valgrind).

Note: I added yesterday another point concerning the KDEDIRS that must
be in ~/.profile to be loaded by KDE desktop when it's starting :
http://www.digikam.org/?q=download/svn#attachments

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 15 November 2006 10:37, Fabien wrote:

> Daniel Bauer wrote:
> > I just wonder about the /usr/local/lib/libexiv2-0.10.so lines, because my
> > svn compiled versions are here: /home/digi/digikamSVN/lib
>
> Yes, that's a problem.
>
> > Do I need another prefix or something for configure?
> >
> > This is what I've done this morning:
>  > [...]
>
> It looks ok. More important, I think, is how you start digikam.
> Try to see lib dependencies with ldd :
> # ldd digikam | grep -i exiv2

digi@venus:~/digikamSVN/bin> ldd digikam | grep -i exiv2
        libexiv2-0.11.so => /home/digi/digikamSVN/lib/libexiv2-0.11.so
(0x405fe000)

this works only in the ~/digikamSVN/bin directory (typed in other directories
it says "ldd: digikam not found"..

>
> It's important to use the environment variables, eg :
> # export DIGIKAMDEST=/opt/digikam
> # export KDEDIRS=$DIGIKAMDEST:/usr
> # export LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH
> # export PATH=$DIGIKAMDEST/bin:$PATH
>
I start it with the adapted script from the webpage:

#!/bin/bash

export DIGIKAMDEST=/home/digi/digikamSVN/
export KDEDIRS=$DIGIKAMDEST:/usr ;
export LD_LIBRARY_PATH=$DIGIKAMDEST/lib:$LD_LIBRARY_PATH ;
export LDPATH=$DIGIKAMDEST/lib:$LDPATH
export PATH=$DIGIKAMDEST/bin:$PATH
hash -r
gdb digikam

> before starting digikam (also with valgrind).

> Note: I added yesterday another point concerning the KDEDIRS that must
> be in ~/.profile to be loaded by KDE desktop when it's starting :
> http://www.digikam.org/?q=download/svn#attachments
>
I've added it to ~/.profile - no change.:

digi@venus:~> ./start_digikam_gdb.sh
GNU gdb 6.3
Copyright [...].
This GDB was configured as "i586-suse-linux"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".

(gdb) run
Starting program: /home/digi/digikamSVN/bin/digikam
[Thread debugging using libthread_db enabled]
[New Thread 1105458432 (LWP 25392)]
kbuildsycoca running...
[New Thread 1109187504 (LWP 25406)]
[Thread 1109187504 (LWP 25406) exited]
[New Thread 1111288752 (LWP 25407)]
[Thread 1111288752 (LWP 25407) exited]
digikam: ScanLib: Nach nicht existierenden Alben suchen: 2 ms
digikam: ScanLib: Nach Einträgen, die nicht in der Datenbank oder auf der
Festplatte sind, suchen: 401 ms
digikam: ScanLib: Einträge ohne Datum werden aktualisiert: 0 ms
digikam: Found dcraw version: 8.41
KIPI (loading): KIPI::PluginLoader: plugin KameraKlient is in the ignore list
for host application
KIPI (loading): Plugin_SlideShow plugin loaded
KIPI (loading): KIPI::PluginLoader: Loaded plugin SlideShow
KIPI (loading): Plugin_SendImages plugin loaded
KIPI (loading): KIPI::PluginLoader: Loaded plugin SendImages
KIPI (loading): Plugin_FindImages plugin loaded
KIPI (loading): KIPI::PluginLoader: Loaded plugin FindImages
terminate called after throwing an instance of 'Exiv2::Error'

Program received signal SIGABRT, Aborted.
[Switching to Thread 1105458432 (LWP 25392)]
0xffffe410 in __kernel_vsyscall ()

(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x41d44541 in raise () from /lib/tls/libc.so.6
#2  0x41d45dbb in abort () from /lib/tls/libc.so.6
#3  0x41cc2489 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#4  0x41cbfe15 in __gxx_personality_v0 () from /usr/lib/libstdc++.so.6
#5  0x41cbfe52 in std::terminate () from /usr/lib/libstdc++.so.6
#6  0x41cbffba in __cxa_throw () from /usr/lib/libstdc++.so.6
#7  0x40680c41 in Exiv2::ExifTags::registerMakerTagInfo (
    ifdId=Exiv2::ifdIdNotSet, tagInfo=0x6) at tags.cpp:1137
#8  0x40679b04 in RegisterMn (this=0x431924a8) at sigmamn.cpp:59
#9  0x4314c2a3 in __static_initialization_and_destruction_0 (
    __initialize_p=<value optimized out>, __priority=<value optimized out>)
    at sigmamn.hpp:148
#10 0x43165dc6 in __do_global_ctors_aux ()
from /usr/local/lib/libexiv2-0.10.so
#11 0x43101425 in _init () from /usr/local/lib/libexiv2-0.10.so
#12 0x4000b9a4 in call_init () from /lib/ld-linux.so.2
#13 0x4000bae1 in _dl_init_internal () from /lib/ld-linux.so.2
#14 0x41e0ded1 in dl_open_worker () from /lib/tls/libc.so.6
#15 0x4000b82f in _dl_catch_error () from /lib/ld-linux.so.2
#16 0x41e0e546 in _dl_open () from /lib/tls/libc.so.6
#17 0x41c0cd68 in dlopen_doit () from /lib/libdl.so.2
#18 0x4000b82f in _dl_catch_error () from /lib/ld-linux.so.2
#19 0x41c0d37e in _dlerror_run () from /lib/libdl.so.2
#20 0x41c0cdc1 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2
#21 0x410ead31 in sys_dl_open () from /opt/kde3/lib/libkdecore.so.4
#22 0x410eb610 in tryall_dlopen () from /opt/kde3/lib/libkdecore.so.4
#23 0x410ed235 in lt_dlopen () from /opt/kde3/lib/libkdecore.so.4
#24 0x410310b6 in KLibLoader::library () from /opt/kde3/lib/libkdecore.so.4
#25 0x40584f8d in KIPI::PluginLoader::loadPlugin ()
   from /home/digi/digikamSVN//lib/libkipi.so.0
#26 0x40585b6f in KIPI::PluginLoader::loadPlugins ()
   from /home/digi/digikamSVN//lib/libkipi.so.0
#27 0x4015f440 in Digikam::DigikamApp::loadPlugins (this=0x8175b58)
    at digikamapp.cpp:1497
#28 0x40164ca6 in DigikamApp (this=0x8175b58) at digikamapp.cpp:170
#29 0x0804a713 in main (argc=1, argv=0xbfe0f2f4) at main.cpp:244
(gdb)

--
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

[Fabien-5]

Daniel Bauer wrote:
> On Wednesday 15 November 2006 10:37, Fabien wrote:

>>Try to see lib dependencies with ldd :
>># ldd digikam | grep -i exiv2
>
>
> digi@venus:~/digikamSVN/bin> ldd digikam | grep -i exiv2
>         libexiv2-0.11.so => /home/digi/digikamSVN/lib/libexiv2-0.11.so
> (0x405fe000)
>
> this works only in the ~/digikamSVN/bin directory (typed in other directories
> it says "ldd: digikam not found"..

Sure. I forgot to say ldd must be followed by the path to the file...

> [...]
>
>>Note: I added yesterday another point concerning the KDEDIRS that must
>>be in ~/.profile to be loaded by KDE desktop when it's starting :
>>http://www.digikam.org/?q=download/svn#attachments
>>
>
> I've added it to ~/.profile - no change.:

Have you restarted the KDE session after modifying this file ?

> digi@venus:~> ./start_digikam_gdb.sh
> GNU gdb 6.3
> Copyright [...].
> This GDB was configured as "i586-suse-linux"...Using host libthread_db
> library "/lib/tls/libthread_db.so.1".
>
> (gdb) run
> Starting program: /home/digi/digikamSVN/bin/digikam
> from /usr/local/lib/libexiv2-0.10.so
> #11 0x43101425 in _init () from /usr/local/lib/libexiv2-0.10.so

 > ...

Could you try to rename this file in order to check if it solves the
problem ?

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 15 November 2006 12:53, Fabien wrote:
> > (gdb) run
> > Starting program: /home/digi/digikamSVN/bin/digikam
> > from /usr/local/lib/libexiv2-0.10.so
> > #11 0x43101425 in _init () from /usr/local/lib/libexiv2-0.10.so
>
>  > ...
>
> Could you try to rename this file in order to check if it solves the
> problem ?

Both installations of Exiv2 releases on the system : 0.10 and 0.11.

This is the problem. Please remove the old Exiv2 library installed on your
system and let's only 0.11 release.

Clean up digikam/DigikamImageplugins _and _ kipi-plugins source code (both use
Exiv2). recompile and install, in first kipi-plugins, in second
digikam/DigikamImagePlugins.

Normally, this will solve your crash problem.

Daniel, if i remember, you use Suse 10.1. Here I have a PIV computer under
Suse 10.1 and i have no crash duing of Exiv2 internal bug (listed in other
mail from this thread). The Exiv2 bug appear in special case (reported
generally on AMD64 computers)

Gilles

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 15 November 2006 12:53, Fabien wrote:

> Daniel Bauer wrote:
> > On Wednesday 15 November 2006 10:37, Fabien wrote:
> >>Try to see lib dependencies with ldd :
> >># ldd digikam | grep -i exiv2
> >
> > digi@venus:~/digikamSVN/bin> ldd digikam | grep -i exiv2
> >         libexiv2-0.11.so => /home/digi/digikamSVN/lib/libexiv2-0.11.so
> > (0x405fe000)
> >
> > this works only in the ~/digikamSVN/bin directory (typed in other
> > directories it says "ldd: digikam not found"..
>
> Sure. I forgot to say ldd must be followed by the path to the file...
>
> > [...]
> >
> >>Note: I added yesterday another point concerning the KDEDIRS that must
> >>be in ~/.profile to be loaded by KDE desktop when it's starting :
> >>http://www.digikam.org/?q=download/svn#attachments
> >
> > I've added it to ~/.profile - no change.:
>
> Have you restarted the KDE session after modifying this file ?
>
> > digi@venus:~> ./start_digikam_gdb.sh
> > GNU gdb 6.3
> > Copyright [...].
> > This GDB was configured as "i586-suse-linux"...Using host libthread_db
> > library "/lib/tls/libthread_db.so.1".
> >
> > (gdb) run
> > Starting program: /home/digi/digikamSVN/bin/digikam
> > from /usr/local/lib/libexiv2-0.10.so
> > #11 0x43101425 in _init () from /usr/local/lib/libexiv2-0.10.so
> >
>  > ...
>
> Could you try to rename this file in order to check if it solves the
> problem ?
>

Fabien,

i have a lot of crash reports duing of dual installations of Exiv2 releases on
computers. Only one Exiv2 instance must be installed on computer. There is no
binary compatibilty between old Exiv2 releases and digiKam will be fragilized
in this case.

I recommend you to post this information somewhere in web site for users wiho
whant to compile digiKam and co. Thanks in advance

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 15 November 2006 12:06, Gilles Caulier wrote:
> Both installations of Exiv2 releases on the system : 0.10 and 0.11.
>
> This is the problem. Please remove the old Exiv2 library installed on your
> system and let's only 0.11 release.

Gilles, when I want to remove exiv2 Yast tells me that ufraw 0.8.1-1 needs it.
And I need ufraw for my cr2's very often...

Is there a stable release exiv2 0.11 somewhere that will work with ufraw AND
digikam? (I need stable versions for my productive work...).

> Clean up digikam/DigikamImageplugins _and _ kipi-plugins source code (both
> use Exiv2). recompile and install, in first kipi-plugins, in second
> digikam/DigikamImagePlugins.
>
> Normally, this will solve your crash problem.
>
> Daniel, if i remember, you use Suse 10.1.

Still on 10.0. I've read too much about problems with 10.1 to give it a try -
never change a running system :-)

> Here I have a PIV computer under
> Suse 10.1 and i have no crash duing of Exiv2 internal bug (listed in other
> mail from this thread). The Exiv2 bug appear in special case (reported
> generally on AMD64 computers)

Here its an "old" intel 32.

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

[Gilles Caulier-2]

On Wednesday 15 November 2006 16:20, Daniel Bauer wrote:

> On Wednesday 15 November 2006 12:06, Gilles Caulier wrote:
> > Both installations of Exiv2 releases on the system : 0.10 and 0.11.
> >
> > This is the problem. Please remove the old Exiv2 library installed on
> > your system and let's only 0.11 release.
>
> Gilles, when I want to remove exiv2 Yast tells me that ufraw 0.8.1-1 needs
> it. And I need ufraw for my cr2's very often...
>
> Is there a stable release exiv2 0.11 somewhere that will work with ufraw
> AND digikam? (I need stable versions for my productive work...).

Well, i don't know, because i compile all myself.

Perhaps somewhere have more informations about Exiv2 Suse packages available
somewhere ?

if no, well, only use the official Exiv2 10.0 package for suse, including
developement package to compile of course.

But, take a care : like developper of Exiv2 project (yes i'm very active
(:=))), i'm must ask you than Exiv2 0.11 is more stable and more improved
than 0.10.

>
> > Clean up digikam/DigikamImageplugins _and _ kipi-plugins source code
> > (both use Exiv2). recompile and install, in first kipi-plugins, in second
> > digikam/DigikamImagePlugins.
> >
> > Normally, this will solve your crash problem.
> >
> > Daniel, if i remember, you use Suse 10.1.
>
> Still on 10.0. I've read too much about problems with 10.1 to give it a try
> - never change a running system :-)

ok

>
> > Here I have a PIV computer under
> > Suse 10.1 and i have no crash duing of Exiv2 internal bug (listed in
> > other mail from this thread). The Exiv2 bug appear in special case
> > (reported generally on AMD64 computers)
>
> Here its an "old" intel 32.

ok

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Fabien-5]

Ok, for the moment, I added a new entry in the FAQ about that :
http://www.digikam.org/?q=node/177

I'm trying to reproduce the bug to find a clean solution.
It should be possible to prevent usage of old libs I hope.

BTW, wouldn't it be possible in digikam to check exiv2 version and send
a warning window at startup ?

Gilles Caulier wrote:

>
> Fabien,
>
> i have a lot of crash reports duing of dual installations of Exiv2 releases on
> computers. Only one Exiv2 instance must be installed on computer. There is no
> binary compatibilty between old Exiv2 releases and digiKam will be fragilized
> in this case.
>
> I recommend you to post this information somewhere in web site for users wiho
> whant to compile digiKam and co. Thanks in advance

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

Le Mercredi 15 Novembre 2006 18:13, Fabien a écrit :

> Ok, for the moment, I added a new entry in the FAQ about that :
> http://www.digikam.org/?q=node/177
>
> I'm trying to reproduce the bug to find a clean solution.
> It should be possible to prevent usage of old libs I hope.
>
> BTW, wouldn't it be possible in digikam to check exiv2 version and send
> a warning window at startup ?
>
> Gilles Caulier wrote:
> > Fabien,
> >
> > i have a lot of crash reports duing of dual installations of Exiv2
> > releases on computers. Only one Exiv2 instance must be installed on
> > computer. There is no binary compatibilty between old Exiv2 releases and
> > digiKam will be fragilized in this case.
> >
> > I recommend you to post this information somewhere in web site for users
> > wiho whant to compile digiKam and co. Thanks in advance

To detect both Exiv2 installation, no because digiKam is linked with Exiv2
library and do not use the command line tool, but we can check the version of
Exiv2 header file available using .configure script just before compilation.

Gilles
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Daniel Bauer-2]

On Wednesday 15 November 2006 12:10, Gilles Caulier wrote:

> Fabien,
>
> i have a lot of crash reports duing of dual installations of Exiv2 releases
> on computers. Only one Exiv2 instance must be installed on computer. There
> is no binary compatibilty between old Exiv2 releases and digiKam will be
> fragilized in this case.
>
> I recommend you to post this information somewhere in web site for users
> wiho whant to compile digiKam and co. Thanks in advance
>
> Gilles

Hi,

it's running now :-)

(I just started it up, didn't test anything, but it started. I'll see how it
works in the next days...)

So as much as I understand, those are the problems (on my System):

        - "unsermake" must be uninstalled despite eventual conflicts
        - "exiv2" other versions must be uninstalled

side notes:

"unsermake" gets automatically installed again on Suse, as soon as one
installs just anything with Yast. So one has to think that after each install
(no matter what) one has to de-install unsermake again before compiling
digikam.

I have been updating all kde stuff to the latest 3.5.5 today and then got a
configure: error: you need to install kdelibs first. In fact kdelibs has been
installed, but the qt3 stuff had to be updatet, too. (Yast didn't tell me
that the existing qt-libs dont work with the updated kde-devel etc.). After
updating qt3 packages configure/make run correct.

regarding my old exiv2: that time I compiled it I used checkinstall instead of
make install to have a rpm. So I can deinstall it now for testing digikam and
reinstall it when using ufraw....

have a nice evening

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

[Fabien-5]

Wow, ok, I can reproduce the bug.
I installed libexiv2-0.10 in /usr/local/lib and digikam crashes at each
startup.
Renaming libexiv2-0.10.so file is enough to solve the problem.
It's really weird, LD_LIBRARY is properly defined everywhere and ldd
results always point to the right library. Why the old one is still loaded ?

Fabien wrote:
> Ok, for the moment, I added a new entry in the FAQ about that :
> http://www.digikam.org/?q=node/177
>
> I'm trying to reproduce the bug to find a clean solution.
> It should be possible to prevent usage of old libs I hope.

--
Fabien

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-2]

On Wednesday 15 November 2006 18:49, Fabien wrote:
> Wow, ok, I can reproduce the bug.
> I installed libexiv2-0.10 in /usr/local/lib and digikam crashes at each
> startup.
> Renaming libexiv2-0.10.so file is enough to solve the problem.
> It's really weird, LD_LIBRARY is properly defined everywhere and ldd
> results always point to the right library. Why the old one is still loaded
> ?

I don't know why exactly. Marcel, are you an explaination for that ?

Normally, digiKam is linked with the first exiv2 version found in the system.
Perhaps because the header file are at the same place (mixed in fact and the
linker mix both library to solve depencies)

Andreas, are you an explaination about why both Exiv2 library release
installed in the system is not cleanly resolved by linker ? Perhaps we need a
lib version tag in shared libexiv2.so file (Not checked the current
implementation of makefile. fix me if it's already done).

Gilles

>
> Fabien wrote:
> > Ok, for the moment, I added a new entry in the FAQ about that :
> > http://www.digikam.org/?q=node/177
> >
> > I'm trying to reproduce the bug to find a clean solution.
> > It should be possible to prevent usage of old libs I hope.
>
> --
> Fabien
>
> _______________________________________________
> Digikam-users mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users