> > . The call to 1604370556.ly caused
> >
> > Error command exited with value 7
> >
> > which is not very helpful...
> >
> > I assume this means `memory exhausted' or something else, since
> > my computer was swapping and swapping and swapping (I have
> > 64MByte main memory).
>
> that is quaint, do you use guile-1.3.4?
Yes.
>Can you check what happens if you try a recent guile from CVS?
Mmhm, not in the near future, sorry...
> > . lilypond looks for the non-CM font `cmti5' which is part of the
> > Sauter extensions. I strongly suggest to add kpathsea support so
> > that such missing fonts can be generated *and found*
> > automatically.
>
> That has been on our wish-list for some time, but we're still
> looking for someone with kpathsea knowledge to do this (hint, hint
> :-)
It's *very* easy for C, but I have no idea how to integrate it in C++,
sorry.
With the latest kpathsea version (i.e. version 3.3 or newer), you only
have to the following four lines to search e.g. cmr10.tfm:
#include <kpathsea/kpathsea.h>
kpse_set_program_name(argv[0], "lilypond");
kpse_init_prog("LILYPOND", 300, "cx", "cmr10");
kpse_find_file("cmr10.tfm", kpse_tfm_format, 1);
That's all. Really. Configuration or support files for lilypond
would be then found in
.:<TEXMF>/lilypond//
which can be adjusted with the environment variable $LILYPONDINPUTS:
kpse_find_file("lily.scm", kpse_program_text_format, 1);
[A similar call exists for getting binary init files.] Of course,
don't use this if you don't want to have lilypond's files integrated
into the TEXMF tree. The various kpsea_xxx_format enum values are
defined in the kpathsea header file `tex-file.h'; a complete list
gives `kpsewhich --help'.
Werner
