- **Needs**:  -->  
- **Patch**: new --> needs_work
- **Type**:  -->  
- **Comment**:

Still fails make - looks a bit different though than before

~~~
...
Making mf/out/feta-braces-b.tfm < mf
Making mf/out/feta-braces-c.tfm < mf
Making mf/out/feta-braces-d.tfm < mf
Making mf/out/feta-braces-e.tfm < mf
Making mf/out/feta-braces-f.tfm < mf
Making mf/out/feta-braces-g.tfm < mf
Making mf/out/feta-braces-h.tfm < mf
Making mf/out/feta-braces-i.tfm < mf
Making mf/out/mf2pt1.mem < mp
Making mf/out/feta11.lisp < log
Making mf/out/feta-noteheads11.lisp < log
Making mf/out/feta-flags11.lisp < log
Making mf/out/feta-alphabet11.lisp < log
Making mf/out/parmesan11.lisp < log
Traceback (most recent call last):
  File "/home/james/lilypond-git/build/scripts/build/out/mf-to-table", line 
164, in <module>
    ['lisp=', 'global-lisp=', ])
  File "/usr/lib/python3.6/getopt.py", line 93, in getopt
    opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
  File "/usr/lib/python3.6/getopt.py", line 157, in do_longs
    has_arg, opt = long_has_args(opt, longopts)
  File "/usr/lib/python3.6/getopt.py", line 174, in long_has_args
    raise GetoptError(_('option --%s not recognized') % opt, opt)
getopt.GetoptError: option --global-lisp not recognized
/home/james/lilypond-git/build/.././mf/GNUmakefile:86: recipe for target 
'out/feta11.lisp' failed
make[1]: *** [out/feta11.lisp] Error 1
make[1]: *** Waiting for unfinished jobs....
Traceback (most recent call last):
  File "/home/james/lilypond-git/build/scripts/build/out/mf-to-table", line 
164, in <module>
    ['lisp=', 'global-lisp=', ])
  File "/usr/lib/python3.6/getopt.py", line 93, in getopt
    opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
  File "/usr/lib/python3.6/getopt.py", line 157, in do_longs
    has_arg, opt = long_has_args(opt, longopts)
  File "/usr/lib/python3.6/getopt.py", line 174, in long_has_args
    raise GetoptError(_('option --%s not recognized') % opt, opt)
getopt.GetoptError: option --global-lisp not recognized
/home/james/lilypond-git/build/.././mf/GNUmakefile:86: recipe for target 
'out/feta-alphabet11.lisp' failed
make[1]: *** [out/feta-alphabet11.lisp] Error 1
Traceback (most recent call last):
  File "/home/james/lilypond-git/build/scripts/build/out/mf-to-table", line 
164, in <module>
    ['lisp=', 'global-lisp=', ])
  File "/usr/lib/python3.6/getopt.py", line 93, in getopt
    opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
  File "/usr/lib/python3.6/getopt.py", line 157, in do_longs
    has_arg, opt = long_has_args(opt, longopts)
  File "/usr/lib/python3.6/getopt.py", line 174, in long_has_args
    raise GetoptError(_('option --%s not recognized') % opt, opt)
getopt.GetoptError: option --global-lisp not recognized
/home/james/lilypond-git/build/.././mf/GNUmakefile:86: recipe for target 
'out/parmesan11.lisp' failed
make[1]: *** [out/parmesan11.lisp] Error 1
Traceback (most recent call last):
Traceback (most recent call last):
  File "/home/james/lilypond-git/build/scripts/build/out/mf-to-table", line 
164, in <module>
  File "/home/james/lilypond-git/build/scripts/build/out/mf-to-table", line 
164, in <module>
    ['lisp=', 'global-lisp=', ])
    ['lisp=', 'global-lisp=', ])
  File "/usr/lib/python3.6/getopt.py", line 93, in getopt
  File "/usr/lib/python3.6/getopt.py", line 93, in getopt
    opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
    opts, args = do_longs(opts, args[0][2:], longopts, args[1:])
  File "/usr/lib/python3.6/getopt.py", line 157, in do_longs
  File "/usr/lib/python3.6/getopt.py", line 157, in do_longs
    has_arg, opt = long_has_args(opt, longopts)
    has_arg, opt = long_has_args(opt, longopts)
  File "/usr/lib/python3.6/getopt.py", line 174, in long_has_args
  File "/usr/lib/python3.6/getopt.py", line 174, in long_has_args
    raise GetoptError(_('option --%s not recognized') % opt, opt)
    raise GetoptError(_('option --%s not recognized') % opt, opt)
getopt.GetoptError: option --global-lisp not recognized
getopt.GetoptError: option --global-lisp not recognized
/home/james/lilypond-git/build/.././mf/GNUmakefile:86: recipe for target 
'out/feta-noteheads11.lisp' failed
make[1]: *** [out/feta-noteheads11.lisp] Error 1
/home/james/lilypond-git/build/.././mf/GNUmakefile:86: recipe for target 
'out/feta-flags11.lisp' failed
make[1]: *** [out/feta-flags11.lisp] Error 1
/home/james/lilypond-git/build/../stepmake/stepmake/generic-targets.make:6: 
recipe for target 'all' failed
make: *** [all] Error 2

~~~



---

** [issues:#5811] mf: use python scripting for generating Emmentaler fonts**

**Status:** Started
**Created:** Sat Feb 29, 2020 08:42 PM UTC by Han-Wen Nienhuys
**Last Updated:** Sat Feb 29, 2020 10:47 PM UTC
**Owner:** Han-Wen Nienhuys


This gets rid of the ugly generated FontForge scripts, and avoids some
intermediate files.

Remove sequencing on |pfb . This was introduced in e6a5019 (Jun 28
2012, "Clean fonts and docs makefiles"). The race conditions were
fixed in f6dc5e (May 15 2014, "Generate a .pe script for one design
size at a time.")

Remove XXX.fontname files. They appear to be unused.

https://codereview.appspot.com/553580043


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to