lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB help needed - fontforge error


From: Jonas Hahnfeld
Subject: Re: GUB help needed - fontforge error
Date: Mon, 27 Apr 2020 17:29:51 +0200
User-agent: Evolution 3.36.1

Am Montag, den 27.04.2020, 15:27 +0100 schrieb Phil Holmes:
> I saw the pull request and so did give it a try.  Jonas you are a magician!
> 
> However, any idea of any magic on this:
> 
> building package: linux-x86::lilypond-test
> *** Stage: download (lilypond-test, linux-x86)
> *** Stage: compile (lilypond-test, linux-x86)
> Running file_sub
> ([('^exec xetex ', 'LD_LIBRARY_PATH= exec xetex ')], 
> '/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/scripts/build/out/xetex-with-options')
> {'use_re': True, 'to_name': None, 'must_succeed': False}
> Traceback (most recent call last):
> File "bin/gub", line 231, in exceptional_build
> build (settings, options, files)
> File "bin/gub", line 227, in build
> b.build_source_packages (names)
> File "bin/../gub/buildrunner.py", line 334, in build_source_packages
> self.spec_build (spec_name)
> File "bin/../gub/buildrunner.py", line 262, in spec_build
> deferred_runner.execute_deferred_commands ()
> File "bin/../gub/runner.py", line 167, in execute_deferred_commands
> cmd.execute (self.logger)
> File "bin/../gub/commands.py", line 271, in execute
> loggedos.file_sub (logger, re_pairs, name, **self.kwargs)
> File "bin/../gub/loggedos.py", line 52, in func_with_logging
> val = logged_function (logger, func, *args, **kwargs)
> File "bin/../gub/loggedos.py", line 19, in logged_function
> return function (*args, **kwargs)
> File "bin/../gub/misc.py", line 557, in file_sub
> s = open (name).read ()
> IOError: [Errno 2] No such file or directory: 
> '/home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/scripts/build/out/xetex-with-options'

Ah, I continue to wonder in how many places things about LilyPond's
build system are hard-coded. You need to globally replace
%(builddir)s/scripts/build/out/
by
%(srcdir)s/scripts/build/
(in gub/specs/lilypond-doc.py and gub/specs/lilypond-test.py AFAICT)

I recently changed this and we're not "compiling" the build scripts
into the out/ directory anymore.

Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]