[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Different GUB failure
From: |
Masamichi HOSODA |
Subject: |
Re: Different GUB failure |
Date: |
Tue, 25 Aug 2015 23:04:01 +0900 (JST) |
>> The Darwin-PPC compile now proceeds fine following the revert. I'm
>> now
>> getting a failure to build the daja-vu fonts: it looks like the font
>> file
>> has not been downloaded:
>>
>> invoking tar -C
>> /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35
>> --strip-component=1 -v -j -xf
>> --/home/gub/NewGub/gub/downloads/fonts-dejavu
>> /dejavu-fonts-ttf-2.35.tar.bz2
>> tar (child): /home/gub/NewGub/gub/downloads/fonts-dejavu/dejavu-fonts-
>> ttf-2.35.tar.bz2: Cannot open: No such file or directory
>>
>> I can confirm that that directory is empty.
>
> I was able to fix the dejavu font problem with Masamichi's suggestion
> of
>
> $ bin/gub --fresh tools::fonts-dejavu
>
> However, the build now fails with the same error with the libertine
> font, which has not been downloaded. I could potentially fix that by
> downloading the font manually, and would probably need to do this for
> all the other new fonts.
>
> But shouldn't this happen automatically as part of the GUB build?
If I understand correctly, GUB downloads automatically, ofcourse.
To build LilyPond, what command do you use?
Is it following?
$ make LILYPOND_BRANCH=release/unstable lilypond
I suspect something like download site or network temporarily problems.