Digicam Tarbell do not have any make files but the settings to build all accordingly with your system.<div><br></div><div>Your low level components dependencies are broken and not suitable to compile<br><br>Le mercredi 16 septembre 2015, Simon Frei <<a href="mailto:freisim93@gmail.com">freisim93@gmail.com</a>> a écrit :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
My system in debian stretch and there actually is a mess going on at
the moment due to gcc 5 transition as I was just confirmed on
another issue. I will revert to an earlier system backup and see
whether the problem persists. I just do not get how this is system
related and how I could debug it for lack of further information, as
makefiles are provided by the digikam tarball.<br>
<br>
<div>On 15/09/15 23:02, Gilles Caulier
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Which system do you use ?
<div><br>
</div>
<div>soprano is not a dependency to libkipi. So it's look like a
configuration mess from your system certainly.</div>
<div><br>
</div>
<div>Gilles Caulier</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-09-15 22:01 GMT+02:00 Simon Frei <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','freisim93@gmail.com');" target="_blank">freisim93@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I tried to
install digikam 4.13 on debian testing via the tarball today
and after a successful run of the bootstrap script make
fails with the following error:<br>
<br>
make[2]: *** No rule to make target
'/usr/lib/libsoprano.so', needed by 'lib/libkipi.so.11.1.0'.
Stop.<br>
CMakeFiles/Makefile2:1961: recipe for target
'extra/libkipi/libkipi/CMakeFiles/kipi.dir/all' failed<br>
make[1]: *** [extra/libkipi/libkipi/CMakeFiles/kipi.dir/all]
Error 2<br>
Makefile:126: recipe for target 'all' failed<br>
make: *** [all] Error 2<br>
<br>
Until now compilation errors usually were unresolved
dependencies with clear error messages, in this case I am
unable to determine the reason and would appreciate any
hints in the right direction.<br>
_______________________________________________<br>
Digikam-users mailing list<br>
<a href="javascript:_e(%7B%7D,'cvml','Digikam-users@kde.org');" target="_blank">Digikam-users@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Digikam-users mailing list
<a href="javascript:_e(%7B%7D,'cvml','Digikam-users@kde.org');" target="_blank">Digikam-users@kde.org</a>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users" target="_blank">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote></div><br><br>-- <br>Send with Gmail Mobile<br>