Re: gub fail/local-build-script/new bug?

[Michael Käppler]

Hi all,

Am 25.01.2020 um 10:02 schrieb Thomas Morley:
> [snip]
> This GUB-build succeded.
> Since I used the most up to date GUB, I suspect the encountered
> problem somewhere in LilyPond not in GUB.
> I'll first make a patched windows-installer (see above) and then I'll
> try to go upstream.
I tried to reproduce the problem, first for the linux-64 target.
So I wiped the gub directory completely and used
current gub
77cd66468e535f1c6c213624be2fd6ca75b685ac
and did
bin/gub linux-64::lilypond

Everything went fine it seems, at least it got through the lilypond
compilation
process. (I did not get your error you got, but IIRC it was the
freebsd-x86 target
that failed for you, right?)
But then I got during lilypond install stage:

invoking cd
/home/dev/gub/target/linux-64/install/lilypond--root/usr/share/lilypond
&& mv 2.21.0 current
invoking cd
/home/dev/gub/target/linux-64/install/lilypond--root/usr/lib/lilypond &&
mv 2.21.0 current
/bin/sh: 1: cd: can't cd to
/home/dev/gub/target/linux-64/install/lilypond--root/usr/lib/lilypond
Command barfed: cd
/home/dev/gub/target/linux-64/install/lilypond--root/usr/lib/lilypond &&
mv 2.21.0 current

I checked this and can confirm that the directory .../usr/lib/lilypond
is missing.
Could not manage to look through 2000+ lines of build log to get a clue
where the
underlying problem is, however.

Cheers,
Michael