Following up the latest build error, I noticed that test-lily/dist-check.py does: ... make --no-builtin-rules local-dist /home/lilypond/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master/./out/lilypond-2.13.2 ...
which therefore triggers: ... make ChangeLog RELEASE-COMMIT make[6]: Entering directory `/home/lilypond/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-master' ... (this all makes sense) HOWEVER, later on in the build, it attempts: ln /home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/ChangeLog /home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/RELEASE-COMMIT /home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/VERSION ... which fails: ln: accessing `/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/ChangeLog': No such file or directory ln: accessing `/home/lilypond/gub/target/linux-x86/src/lilypond-git.sv.gnu.org--lilypond.git-master/RELEASE-COMMIT': No such file or directory Why is it attempting to link from the ../src/.. dir, instead of the ../build/.. dir? I mean, we shouldn't expect to see any generated files like ChangeLog or RELEASE-COMMIT in that dir, should we? Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
