"Install digiKam in your Home Directory" wouldn't work :-(
Locked
12
12
 
|
Ok, I think I understood the problem.
In my first try, I forgot to check the lib/kde3 subdir that contains imageplugins and kipiplugins. When I started digikam with strace, I saw that it was a kipiplugin that loaded the old lib. All kipiplugins that needed libexiv2 were linked to the old exiv2 lib. Here's the reason : In my compile script, I didn't use the --with-extra-libs for kipiplugins... I'm doing more tests right now but I think this should fix the problem... Gilles Caulier wrote: > 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). -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Ok, it looks better now :)
I modified the download/svn page to add that. http://www.digikam.org/?q=download/svn Fabien wrote: > Ok, I think I understood the problem. > > In my first try, I forgot to check the lib/kde3 subdir that contains > imageplugins and kipiplugins. > > When I started digikam with strace, I saw that it was a kipiplugin that > loaded the old lib. > > All kipiplugins that needed libexiv2 were linked to the old exiv2 lib. > > > Here's the reason : > In my compile script, I didn't use the --with-extra-libs for kipiplugins... > > I'm doing more tests right now but I think this should fix the problem... -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Daniel Bauer-2
Hi,
Daniel Bauer wrote: > On Wednesday 15 November 2006 12:10, Gilles Caulier wrote: > > it's running now :-) Ok, fine ! > (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 For this point, it should be ok now, with the latest compile script that adds the --with-extra-libs=$DIGIKAMDEST/lib For unsermake, there should be a solution. What looks not normal for me is that usermake could be used for the default make command... But, in any case, using gmake and only gmake should solve the problem. It's difficult to reproduce it because even if I install it, I still have gmake as the default make. I may try to install opensuse :) > 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 guess it's because it's a dependency for one other package, so each time you install something, it will try to solve dependencies problems... -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: "Install digiKam in your Home Directory"
|
|
On Thursday 16 November 2006 11:37, Fabien wrote:
> Hi, > > Daniel Bauer wrote: > > On Wednesday 15 November 2006 12:10, Gilles Caulier wrote: > > > > it's running now :-) > > Ok, fine ! > > > (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 > > For this point, it should be ok now, with the latest compile script that > adds the --with-extra-libs=$DIGIKAMDEST/lib > > For unsermake, there should be a solution. > What looks not normal for me is that usermake could be used for the > default make command... But, in any case, using gmake and only gmake > should solve the problem. It's difficult to reproduce it because even if > I install it, I still have gmake as the default make. > I may try to install opensuse :) no need. i have opensuse here (:=))) In fact the package depencies is dummy. Sounds like all automake depencies in packages have been remplaced by unsermake (tested with all kdevelop packages). If i have installed automake after to have installed kdevelop, suse said than unsermake must be uninstalled _and_ also all package witch use unsermake... like kdevelop & co. Like unsermake must be an automake program (fully compatible in fact), this depency is a non-sence. To solve the problem, force to uninstall unsermake without checking depencies, and install automake instead. This will working fine. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: "Install digiKam in your Home Directory"
|
|
In reply to this post by Fabien-5
On Thu, 16 Nov 2006, Fabien wrote:
[...] > All kipiplugins that needed libexiv2 were linked to the old exiv2 lib. > > Here's the reason : > In my compile script, I didn't use the --with-extra-libs for kipiplugins... > > I'm doing more tests right now but I think this should fix the problem... At some point (I forgot which) I also had to specify the extra-includes: --with-extra-includes=$DST/include --with-extra-libs=$DST/lib *Maybe* one does not see any problems as long as the header files are unchanged between the different versions. Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Arnd Baecker wrote:
> On Thu, 16 Nov 2006, Fabien wrote: > > [...]> > >>All kipiplugins that needed libexiv2 were linked to the old exiv2 lib. >> >>Here's the reason : >>In my compile script, I didn't use the --with-extra-libs for kipiplugins... >> >>I'm doing more tests right now but I think this should fix the problem... > > > At some point (I forgot which) I also > had to specify the extra-includes: > > --with-extra-includes=$DST/include --with-extra-libs=$DST/lib It was already in the script :) -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: "Install digiKam in your Home Directory"
|
|
In reply to this post by Fabien-5
On Thursday 16 November 2006 11:37, Fabien wrote:
> > - "exiv2" other versions must be uninstalled > > For this point, it should be ok now, with the latest compile script that > adds the --with-extra-libs=$DIGIKAMDEST/lib > Fabien Thanks for your work and time! I've re-installed "my" exiv2 (so that now I have the old and the new svn-one), compiled digikam with the additional "--with-extra-libs..." - and now it starts up fine. With unsermake it is just as Gilles said (of course ;-) ) : when de-installing it, Yast complains, but if I ignore it, there's nobody else in my computer who misses it. The only thing is to always think about de-installing unsermake again after any other install via Yast, because Yast every time automatically installs it due to this "non-sense depency" (© Gilles). I'll post this issue to the opensuse mailing list, maybe there's a solution (or a reason). Now I'm looking forward to work with the new version. I have a 480 pictures session which I will try to work with 0.9svn. I'm very curious now... kind regards Daniel b.t.w.: I still only receive part of the list emails and then very delayed. Is this a known problem here or a problem of my ISP? -- 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 |
Re: "Install digiKam in your Home Directory"
|
|
In reply to this post by Fabien-5
On Thu, 16 Nov 2006, Fabien wrote:
> Arnd Baecker wrote: [...] > > At some point (I forgot which) I also > > had to specify the extra-includes: > > > > --with-extra-includes=$DST/include --with-extra-libs=$DST/lib > > It was already in the script :) Hmm, I should have seen that ;-) Anyway, I am just testing your notes, and everything seems to work fine. Just a few comments: - the files to download are *.txt (and not *.sh) - I cannot get any of the help texts to work: For help (eg. via F1) I get: """The requested help file could not be found. Check that you have installed the documentation.""" It is most likely that this is due to the way I installed things. (Though I don't know how to do this one right). Does this work for you? - Near the end of the text at http://www.digikam.org/?q=download/svn you write: """Important:if you run another KDE application (eg KDE Desktop, any k*** tool) before defining the KDEDIRS environment variable, digikam won't work or not correctly.""" One could add: """Sometimes it works to do the exports as in start_digikam.sh at the shell prompt and then run kdeinit""" (At least that did work for me this time ;-) - Just out of curiosity: do you have a 4 CPU machine, or why do you use make -j 4? So your scripts work very well - many thanks!!! Best, Arnd _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Arnd Baecker wrote:
> On Thu, 16 Nov 2006, Fabien wrote: > > >>Arnd Baecker wrote: > > [...] > > Anyway, I am just testing your notes, and everything seems > to work fine. > Just a few comments: > - the files to download are *.txt > (and not *.sh) Yes, I know. At the beginning, it was because it was not allowed to upload .sh files with drupal. Afterward, I found where I can change this configuration. But, I'm not sure it's a good idea. I prefer people to check the files and think a bit before executing them :) > - I cannot get any of the help texts to work: > For help (eg. via F1) I get: > """The requested help file could not be found. Check that you have > installed the documentation.""" > It is most likely that this is due to the way I installed things. > (Though I don't know how to do this one right). Hmm, right. There are 2 problems : - khelpcenter doesn't use the KDEDIRS when it looks for documentation, it only looks in /usr/share/doc/kde (at least with my configuration) I didn't find a way to specify additional paths for dirs. I'm not even sure it's possible... I tried to symlink the directory and it works. But that's not very clean :( - documentation is not installed for digikam with my script, only kipi-plugins. I will try to fix that (the doc/ directory is not checked out by svn). > - Near the end of the text at > http://www.digikam.org/?q=download/svn > you write: > """Important:if you run another KDE application > (eg KDE Desktop, any k*** tool) before defining > the KDEDIRS environment variable, digikam won't work > or not correctly.""" > > One could add: > """Sometimes it works to do the exports as in start_digikam.sh > at the shell prompt and then run kdeinit""" > (At least that did work for me this time ;-) I did some quick tests and it seems to work for me too ! I'm not sure it works in all condition, but I will add that. > - Just out of curiosity: > do you have a 4 CPU machine, or why do you use make -j 4? Well, yes :)) I did some tests on a dual Amd Opteron dualcore. It was a bit faster to compile digikam on this compute server ;-) > So your scripts work very well - many thanks!!! Thanks for your report. -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Fabien wrote:
> Arnd Baecker wrote: > [...] >>- Near the end of the text at >> http://www.digikam.org/?q=download/svn >> you write: >> """Important:if you run another KDE application >> (eg KDE Desktop, any k*** tool) before defining >> the KDEDIRS environment variable, digikam won't work >> or not correctly.""" >> >> One could add: >> """Sometimes it works to do the exports as in start_digikam.sh >> at the shell prompt and then run kdeinit""" >> (At least that did work for me this time ;-) > > > I did some quick tests and it seems to work for me too. > I'm not sure it works in all condition, but I will add that. > Ok, done. http://www.digikam.org/?q=download/svn -- Fabien _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |