<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 20, 2015, at 12:46 AM, Willem Ferguson <<a href="mailto:willemferguson@zoology.up.ac.za" class="">willemferguson@zoology.up.ac.za</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class="">
<div class="moz-cite-prefix">On 19/04/2015 22:08, Robert C. Helling
wrote:<br class="">
</div>
<blockquote cite="mid:C3B1628C-D6BD-4633-9A2E-B11EFB8FDB24@atdotde.de" type="cite" class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
Willem,
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 19 Apr 2015, at 20:24, Willem Ferguson <<a moz-do-not-send="true" href="mailto:willemferguson@zoology.up.ac.za" class="">willemferguson@zoology.up.ac.za</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align: start;
text-indent: 0px; text-transform: none; white-space:
normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; float: none; display:
inline !important;" class="">Anything I could do now?</span><br style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Helvetica; font-size: 12px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
float: none; display: inline !important;" class="">I
know there is currently a lot of activity to get the
build to run smoothly.</span><br style="font-family:
Helvetica; font-size: 12px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans:
auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<div class="">with git grep I get the impression this is once more
a problem with the version of libgit2 (has to be quite recent).
I would have thought the build script does download that but I
would investigate the version installed on your system.</div>
<div class=""><br class="">
</div>
<div class="">Best</div>
<div class="">Robert</div>
<br class="">
</blockquote>
I had libgit2 v0.19 in my system and v0.22 in the src directory. I
removed v0.19 from the system, leaving only the version in the src
directory.<br class="">
<br class="">
It aborts two steps earlier in the process with a slightly different
error message. Looks like libgit2 is a real obstacle.<br class="">
<br class="">
[ 23%] Built target subsurface_corelib<br class="">
make[2]: *** No rule to make target
`/usr/lib/x86_64-linux-gnu/libgit2.a', needed by `TestGpsCoords'.
Stop.<br class="">
make[1]: *** [CMakeFiles/TestGpsCoords.dir/all] Error 2<br class="">
make: *** [all] Error 2<br class="">
willem@dive:~/src$ <br class="">
<br class=""></div></div></blockquote><div><br class=""></div><div><br class=""></div>The thing that’s annoying is that even if we build libgit2 from source, cmake seems to pick the system installed one over ours.</div><div>I’ve had that happen as well, but don’t understand the FindXXX() functions enough to figure out why that is. But as it happens I’ll be hanging out with Tomaz for the next few days and I’ll beat him with a stick until he fixes this.</div><div>OK, maybe not beat him. Maybe I’ll just ask nicely :-)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
I am not clear on what build.sh does with libigit2. I would have
expected that the install instruction (line 55 in build.sh) installs
libgit2 in the appropriate system folder. But a locate command on
libgit2 on my machine now only shows files in the home/src
directory, not in /lib/ or a similar directory. From what I can see
from the error message, the make process aborts while trying to make
use of libgit2 to build Subsurface. This means that a valid object
file for libgit2 exists??<br class=""></div></div></blockquote><br class=""></div><div>No, we don’t install anything in system directories. We install into our install-root.</div><div><br class=""></div><div>/D</div><br class=""></body></html>