I wanted to commit this, but first I tried to build it and I'm getting
link failure on Linux, both with (the patch and libgit2-0.22) and also
with (no patch and libgit2-0.20). The wierd thing is, last April I
successfully built it with libgit2-0.20, and my installation of
libgit2-0.20 hasn't been touched since then, and the ra-git branch
branch hasn't been touched since then.
What has changed? My build script has changed (the options I pass to
Subversion's 'configure', for instance), and I've upgraded my OS from
Ubuntu 12.04 to Ubuntu 14.04.
One approach I could take is to debug what's going wrong in the
linking, and figure out the root cause from there. But before
bothering with that, can anyone else build it? It seems likely it's a
problem local to me.
- Julian
On 31 March 2015 at 00:28, James McCoy <jamessan_at_debian.org> wrote:
> On Tue, Mar 31, 2015 at 12:13:09AM +0200, Branko Čibej wrote:
>> On 30.03.2015 20:26, Daniel Shahaf wrote:
>> > Carlos Martín Nieto wrote on Mon, Mar 30, 2015 at 16:58:57 +0200:
>> >> +++ autogen.sh (working copy)
>> >> - configfile=${LIBTOOL_CONFIG-`cd $ltpath/../share/libtool/config ; pwd`/$file}
>> >> + configfile=${LIBTOOL_CONFIG-$(cd $ltpath/../share/libtool/config ; pwd)}/$file
>> > Is it safe to use $(...)?
>>
>> It is not. autogen.sh must not require bash.
>
> $(...) isn't a bash-ism. It's specified by POSIX[0].
>
> [0]: http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03
>
> Cheers,
> --
> James
> GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <jamessan_at_debian.org>
>
Received on 2015-03-31 13:20:13 CEST