[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "make check" in gnulib requires cppi
From: |
Jim Meyering |
Subject: |
Re: "make check" in gnulib requires cppi |
Date: |
Thu, 01 Sep 2011 09:27:13 +0200 |
Bernhard Voelker wrote:
> On 09/01/2011 08:37 AM, Jim Meyering wrote:
>> Bernhard Voelker wrote:
>>> After
>>> git checkout master&& git pull
>>> "make check" fails in gnulib on my OpenSuSE 11.4 system
>>> because cppi is not installed:
>>
>> Thanks for the report.
>> However, ...
>
> Thanks for the quick answer!
>
>>> berny@blackice:~/git/coreutils> make check
>>> GEN public-submodule-commit
>>> fatal: Not a valid commit name 9926b90d5159916a539b49359b3589fe89c2d987
>>> /usr/lib/git/git-submodule: line 299: test:
>>> 9926b90d5159916a539b49359b3589fe89c2d987: unary operator expected
>>> Stopping at 'gnulib'; script returned non-zero status.
>>> maint.mk: found non-public submodule commit
>>
>> Have you updated your master gnulib directory?
>> The one you pointed to via ./bootstrap --gnulib-srcdir=...
>> Once you do that, coreutils' bootstrap should get past the above.
>
> As HACKING and README-hacking suggest, I started once with
>
> git clone git://git.sv.gnu.org/coreutils
>
> but left out the optional step
>
> export GNULIB_SRCDIR=/path/to/gnulib
>
> so it cloned gnulib into coreutils/gnulib.
> Then I continued with
>
> cd coreutils
> ./bootstrap
> git submodule foreach git pull origin master
> ...
>
> I thought this would be sufficient. I'm a bit confused about
> stacked git repositories (used to work with ClearCase for many
> years). Is there a way out?
If you do this,
(cd gnulib && git checkout master && git pull)
Then ./bootstrap should "make check" should pass that test.