>> URW++ and TeX Gyre
>> Bitstream Vera Sans
>> Bitstream Charter
>> DejaVu Sans
>> DejaVu Serif
>> DejaVu Sans Mono
>> Linux Libertine O
>> Have you installed these fonts?
>
> I had only DejaVu, URW and Gyre.
>
> I'm used to run `dnf builddep` to get the build dependencies in
> Fed
Il giorno mar 29 lug 2025 alle 03:12:32 +00:00:00, Werner LEMBERG
ha scritto:
Actually, for running `make doc` this problem of yours shouldn't
happen at all – if you install the necessary fonts for building the
documentation, these fall-back fonts should never be accessed.
Have you seen chapter
> The very reason the problem occurs is that Federico's
> `NotoSerifCJK-VF.ttc` is actually the renamed font file
> `NotoSerifCJK-VF.otf.ttc`, and this font uses the 'CFF2' format.
> Such fonts can't be embedded into a PS file; consequently we get an
> error. [...]
>
> I'll submit a PR to make Li
> Eventually I decided to remove the package, as no package depended
> on it.
>
> Then I got the same error on other fonts: NotoSansMonoCJKjp-Regular
> and maybe another one.
>
> So, to summarize, I removed these packages:
>
> google-noto-serif-cjk-vf-fonts
> google-noto-sans-cjk-vf-fonts
> goog
Il giorno lun 28 lug 2025 alle 17:53:47 +00:00:00, Werner LEMBERG
ha scritto:
A solution to this particular problem is now easy: Replace
`NotoSerifCJK-VF.otf.ttc` with the fully equivalent (but slightly
larger) file `NotoSerifCJK-VF.ttf.ttc`, which can be found here:
https://github.co
>> A solution to this particular problem is now easy: Replace
>> `NotoSerifCJK-VF.otf.ttc` with the fully equivalent (but slightly
>> larger) file `NotoSerifCJK-VF.ttf.ttc`, which can be found here:
>> https://github.com/notofonts/noto-cjk/blob/main/Serif/Variable/OTC/NotoSerifCJK-VF.ttf.ttc
>
>
Il giorno lun 28 lug 2025 alle 10:22:34 +00:00:00, Werner LEMBERG
ha scritto:
A solution to this particular problem is now easy: Replace
`NotoSerifCJK-VF.otf.ttc` with the fully equivalent (but slightly
larger) file `NotoSerifCJK-VF.ttf.ttc`, which can be found here:
https://github.com/notof
>> I see, thanks. Alas, this is actually another bug in FontConfig;
>> it doesn't properly handle Font Variations in TTCs. I've reported
>> it just now as
>>
>> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/488
>
> After some more thinking I now believe that this is a bug in
> L
>> /usr/share/fonts/google-noto-serif-cjk-vf-fonts/NotoSerifCJK-VF.ttc
>
> I see, thanks. Alas, this is actually another bug in FontConfig; it
> doesn't properly handle Font Variations in TTCs. I've reported it
> just now as
>
> https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/48
>> Which font file is this? Looking into Google's 'noto-cjk' git
>> repository, there are multiple choices:
>> NotoSerifCJK-ExtraLight.ttc
>> NotoSerifCJKjp-ExtraLight.otf
>> NotoSerifCJK-VF.otf.ttc
>> NotoSerifCJK-VF.ttf.ttc
>> NotoSerifCJKjp-VF.otf
>> NotoSerifCJKjp-VF.ttf
>>
>
>
Il giorno dom 27 lug 2025 alle 16:47:24 +00:00:00, Werner LEMBERG
ha scritto:
[...] but now I'm getting a new error:
warning: Font NotoSerifCJKjp-ExtraLight cannot be used in PostScript
resource directory because it is unknown format.
Which font file is this? Looking into Google's '
> [...] but now I'm getting a new error:
>
> warning: Font NotoSerifCJKjp-ExtraLight cannot be used in PostScript
> resource directory because it is unknown format.
Which font file is this? Looking into Google's 'noto-cjk' git
repository, there are multiple choices:
NotoSerifCJK-ExtraLight.t
> For the time being, please modify `99-lilypond-fonts.conf` as
> suggested in that issue; I'll submit a PR that adds this
> automatically to LilyPond if FontConfig >= 2.15 is found on the
> system.
This is now
https://gitlab.com/lilypond/lilypond/-/merge_requests/2702
Werner
Il giorno dom 27 lug 2025 alle 11:13:27 +00:00:00, Werner LEMBERG
ha scritto:
For the time being, please modify `99-lilypond-fonts.conf` as
suggested in that issue; I'll submit a PR that adds this automatically
to LilyPond if FontConfig >= 2.15 is found on the system.
Thank you, it helped to m
>>> If you compile LilyPond from scratch please retry a compilation
>>> with a FontConfig version equal to or larger than 2.15 –
>>> theoretically, Variation Fonts should be rejected correctly. If
>>> you can't or won't do that you have to replace the VFs with non-VF
>>> versions.
>>
>> I compile
>> If you compile LilyPond from scratch please retry a compilation
>> with a FontConfig version equal to or larger than 2.15 –
>> theoretically, Variation Fonts should be rejected correctly. If
>> you can't or won't do that you have to replace the VFs with non-VF
>> versions.
>
> I compiled Lily
Il giorno dom 27 lug 2025 alle 10:01:06 +00:00:00, Werner LEMBERG
ha scritto:
A similar problem with the Noto family has been recently discussed:
https://lists.gnu.org/archive/html/lilypond-user/2025-07/msg00073.html
If you compile LilyPond from scratch please retry a compilation with a
Fo
> fatal error: Font NotoSerif-Bold cannot be loaded via Ghostscript
> because its font-index (262144) is not zero.
>
> Noto is the default font in Fedora since a few versions.
> I've just installed texlive-noto, re-run the build command but I get
> the same error.
>
> I know you are the best pers
Il giorno dom 27 lug 2025 alle 08:56:12 +00:00:00, Werner LEMBERG
ha scritto:
snippet-names-9f571599ce826614c623dd2bc0ba6fe9.ly contains a long
list of file names. Which one is causing the failure?
There should be a file
out/lybook-db/snippet-names-9f571599ce826614c623dd2bc0ba6fe9.lo
> snippet-names-9f571599ce826614c623dd2bc0ba6fe9.ly contains a long
> list of file names. Which one is causing the failure?
There should be a file
out/lybook-db/snippet-names-9f571599ce826614c623dd2bc0ba6fe9.log
What does it say?
Werner
On 2024-11-30 13:37, Jean-Charles Malahieude wrote:
On a fresh repo, make doc chokes on
input/regression/include-path-modification and I'm unable to resolve this.
Excerpt of the log:
```
Renaming input to: `include-path-modification-i.ly'
include-path-modification-i.ly:13:2: error: Guile signa
Am So., 29. Nov. 2020 um 19:32 Uhr schrieb Werner LEMBERG :
>
>
> >> At the beginning of `internals.texi2pdf.log`:
> >>
> >> {finger
> >>
> >> /home/hermann/lilypond-git/build/Documentation/out-www/en/internals.texi:1659:
> >> Paragraph ended before @var was complete.
> >>
> >>
>> At the beginning of `internals.texi2pdf.log`:
>>
>> {finger
>>
>> /home/hermann/lilypond-git/build/Documentation/out-www/en/internals.texi:1659:
>> Paragraph ended before @var was complete.
>>
>> @par
>> l.1659
>>
>> I guess you missed a `@`...
>>
>>
>> Wer
Am So., 29. Nov. 2020 um 19:15 Uhr schrieb Werner LEMBERG :
>
>
> > while preparing a patch, I couldn't build the docs on my local branch
> > for unknown reasons.
>
> At the beginning of `internals.texi2pdf.log`:
>
> {finger
>
> /home/hermann/lilypond-git/build/Documentation/out-www/en/interna
> while preparing a patch, I couldn't build the docs on my local branch
> for unknown reasons.
At the beginning of `internals.texi2pdf.log`:
{finger
/home/hermann/lilypond-git/build/Documentation/out-www/en/internals.texi:1659:
Paragraph ended before @var was complete.
On 29/11/2020 17:26, Thomas Morley wrote:
Hi,
while preparing a patch, I couldn't build the docs on my local branch
for unknown reasons.
Making sure it works at all, I switched to master out of
e7d976fe5f0777c347927eb79e1b4e312921773f
and tried:
~/lilypond-git/build (master)$ make LANGS='en' do
On 31/07/2020 22:04, Daniel Benjamin Miller wrote:
It's actually quite fine. It's basically saying it can't find Gyre or
Emmentaler in GhostScript's bundled fonts. Which it shouldn't, since
they're not included with GS. It finds it instead in the LilyPond
build directory, where it well should b
On 6/17/20, Valentin Villenave wrote:
> Thanks for giving me hope, even for a minute :-)
I spoke too soon; running doc-clean and _then_ “make doc” indeed fixes
the problem. (And Jonas has just merged it onto master so that
problem is fixed.)
Thanks!
Cheers,
-- V.
On 6/17/20, Michael Käppler wrote:
> Do you have
> https://gitlab.com/lilypond/lilypond/-/merge_requests/148/diffs?commit_id=c002d5e8c2e737cefbafa84f4b66e4b3bbc6d111
> in your repo? Otherwise that may well be the problem. Jonas wanted to
> push this one yesterday,
> but it seems that did not happe
Am Mittwoch, den 17.06.2020, 10:59 +0200 schrieb Michael Käppler:
> Am 17.06.2020 um 10:52 schrieb Valentin Villenave:
> > Greetings everyone,
> > I’ve noticed a recent regression with `make doc’: when it reaches
> > Documentation/ly-examples, gs fails on a bunch of files with the
> > following err
Am 17.06.2020 um 10:52 schrieb Valentin Villenave:
Greetings everyone,
I’ve noticed a recent regression with `make doc’: when it reaches
Documentation/ly-examples, gs fails on a bunch of files with the
following error message:
Command: /home/work/lilypond/out/bin/lilypond -dpreview
-dresolution=
On 4/23/20, Federico Bruni wrote:
> I confirm it's a stale dependency file.
> I had the same problem while testing my patch before pushing and IIRC
> removing Documentation/it/out-www/web.texi fixed it.
OK, thanks! I should have thought about doc-clean.
Cheers,
- V.
Il giorno gio 23 apr 2020 alle 16:01, Jonas Hahnfeld via Discussions on
LilyPond development ha scritto:
Am Donnerstag, den 23.04.2020, 13:37 + schrieb Valentin Villenave:
Hey everybody,
For the past few days, I’ve been unable to make doc because of the
following error:
*** No rule
Am Donnerstag, den 23.04.2020, 13:37 + schrieb Valentin Villenave:
> Hey everybody,
> For the past few days, I’ve been unable to make doc because of the
> following error:
>
> *** No rule to make target
> '/home/work/lilypond/Documentation/it/web/news-headlines.itexi',
> needed by 'out-www/web
On Mon, Feb 24, 2020 at 10:44 PM David Kastrup wrote:
> > The result is 25 minutes of purely CPU bound grinding (this is with
> > Guile 2.2). Then building the remaining docs takes about 15 minutes.
> > In this last phase, there is some inefficiency: we process the
> > documents per language direc
David Kastrup writes:
> Han-Wen Nienhuys writes:
>
>> I tried what happens if one concats all texi/tely files together, and
>> runs lp-book on them.
>>
>> The result is 25 minutes of purely CPU bound grinding (this is with
>> Guile 2.2). Then building the remaining docs takes about 15 minutes.
>
Han-Wen Nienhuys writes:
> I tried what happens if one concats all texi/tely files together, and
> runs lp-book on them.
>
> The result is 25 minutes of purely CPU bound grinding (this is with
> Guile 2.2). Then building the remaining docs takes about 15 minutes.
> In this last phase, there is so
Knut,
On Mon, 9 Jul 2018 20:46:06 +0200, Knut Petersen
wrote:
> Am 16.06.2018 um 15:47 schrieb James Lowe:
> > Hello
> >
> > On Sat, 16 Jun 2018 14:20:43 +0100 (BST), "James Lowe"
> > wrote:
> >
> >> Hello
> >>
> >> On Sat, 16 Jun 2018 09:10:10 -0400, Dan Eble wrote:
> >>
> >>> On Jun 16, 20
Am 16.06.2018 um 15:47 schrieb James Lowe:
Hello
On Sat, 16 Jun 2018 14:20:43 +0100 (BST), "James Lowe"
wrote:
Hello
On Sat, 16 Jun 2018 09:10:10 -0400, Dan Eble wrote:
On Jun 16, 2018, at 08:46, James Lowe wrote:
Well before I applied those patches on behalf of Alexander's patches I d
Hello
On Sat, 16 Jun 2018 14:20:43 +0100 (BST), "James Lowe"
wrote:
> Hello
>
> On Sat, 16 Jun 2018 09:10:10 -0400, Dan Eble wrote:
>
> > On Jun 16, 2018, at 08:46, James Lowe wrote:
> > >
> > > Well before I applied those patches on behalf of Alexander's patches I
> > > did a full patch
Hello
On Sat, 16 Jun 2018 09:10:10 -0400, Dan Eble wrote:
> On Jun 16, 2018, at 08:46, James Lowe wrote:
> >
> > Well before I applied those patches on behalf of Alexander's patches I did
> > a full patch test with the patches applied and had no problems.
> >
> > However ... I know that ther
On Jun 16, 2018, at 08:46, James Lowe wrote:
>
> Well before I applied those patches on behalf of Alexander's patches I did a
> full patch test with the patches applied and had no problems.
>
> However ... I know that there are some 'prgramming errors' reported that do
> not break patch testin
Hello,
On Sat, 16 Jun 2018 14:21:28 +0200, David Kastrup wrote:
>
> I get the following:
>
> lilypond-book.py: error: `musicxml2ly --out=- - ' failed (0)
> lilypond-book.py: error: The error log is as follows:
> musicxml2ly: Reading MusicXML from Standard input ...
> musicxml2ly: Converting t
David Kastrup writes:
> I get the following:
>
> lilypond-book.py: error: `musicxml2ly --out=- - ' failed (0)
> lilypond-book.py: error: The error log is as follows:
> musicxml2ly: Reading MusicXML from Standard input ...
> musicxml2ly: Converting to LilyPond expressions...
> Traceback (most rec
2018-02-06 13:17 GMT+01:00 James Lowe :
> Hello,
>
> On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
> wrote:
>
>> Hi,
>>
>> I'm still trying to get make doc work again for my guilev2 setup.
>> It now fails at a point I'm not able to surely track down.
>>
>> The only suspicious in the log I'm po
Hello,
On Mon, 5 Feb 2018 22:36:51 +0100, Thomas Morley
wrote:
> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
2018-02-05 23:59 GMT+01:00 Thomas Morley :
> 2018-02-05 23:48 GMT+01:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>>
Uh, you are aware that your log ends with:
Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core
2018-02-05 23:48 GMT+01:00 David Kastrup :
> Thomas Morley writes:
>
>> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>>
>>>
>>> Uh, you are aware that your log ends with:
>>>
>>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>>
>>> The programming errors are a nuisance
Thomas Morley writes:
> 2018-02-05 23:23 GMT+01:00 David Kastrup :
>
>>
>> Uh, you are aware that your log ends with:
>>
>> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>>
>> The programming errors are a nuisance (and should likely get fixed) but
>> this aborts for
2018-02-05 23:23 GMT+01:00 David Kastrup :
>
> Uh, you are aware that your log ends with:
>
> Writing ./f4/lily-265fe61c-systems.count...Segmentation fault (core dumped)
>
> The programming errors are a nuisance (and should likely get fixed) but
> this aborts for entirely different reasons.
Yes,
Thomas Morley writes:
> Hi,
>
> I'm still trying to get make doc work again for my guilev2 setup.
> It now fails at a point I'm not able to surely track down.
>
> The only suspicious in the log I'm pointed to is:
>
> Processing `./15/lily-ef5769c9.ly'
> Parsing...
> Renaming input to: `modifying-
>>> So do we need any warnings or notes to be added to here:
>>>
>>> http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
>>>
>>> and/or here:
>>>
>>> http://lilypond.org/doc/v2.19/Documentation/notation-big-page#entire-document-fonts
>>>
>>> ?
>> In
Hosoda-san,
On 07/06/16 13:54, Masamichi Hosoda wrote:
So do we need any warnings or notes to be added to here:
http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
and/or here:
http://lilypond.org/doc/v2.19/Documentation/notation-big-page#enti
>>> Any idea why this is so? Could you contact the gs people by filing
>>> a bug report so that we get an explanation?
>>
>> If I understand correctly, there is four issues at least. [...]
>
> Thanks for your analysis.
There is ghostscript developers reply.
http://bugs.ghostscript.com/show_bug
> So do we need any warnings or notes to be added to here:
>
> http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond
>
> and/or here:
>
> http://lilypond.org/doc/v2.19/Documentation/notation-big-page#entire-document-fonts
>
> ?
In my humble opini
Hosoda-san,
On 06/06/16 14:44, Masamichi Hosoda wrote:
I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
So most Japanese fonts can not be used with `-dgs-load-fonts'
option.
Any idea why this is so? Could you contact the gs people by filing a
bug report so that we get an e
>> Any idea why this is so? Could you contact the gs people by filing
>> a bug report so that we get an explanation?
>
> If I understand correctly, there is four issues at least. [...]
Thanks for your analysis.
Werner
___
lilypond-devel mailin
>> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
>>
>> So most Japanese fonts can not be used with `-dgs-load-fonts'
>> option.
>
> Any idea why this is so? Could you contact the gs people by filing a
> bug report so that we get an explanation?
If I understand correctly,
> I've tried some Japanese fonts with `-dgs-load-fonts' option. [...]
>
> So most Japanese fonts can not be used with `-dgs-load-fonts'
> option.
Any idea why this is so? Could you contact the gs people by filing a
bug report so that we get an explanation?
Werner
___
>>> In addition, all fonts of the above without `-dgs-load-fonts' option are
>>> fine.
>>> I suggest removing `-dgs-load-fonts' option from lilypond-book.
>>> I think that `--bigpdfs' option is more suitable than
>>> `-dgs-load-fonts'.
>>
>> Either make for particularly large PDF files, don't the
>> In addition, all fonts of the above without `-dgs-load-fonts' option are
>> fine.
>> I suggest removing `-dgs-load-fonts' option from lilypond-book.
>> I think that `--bigpdfs' option is more suitable than
>> `-dgs-load-fonts'.
>
> Either make for particularly large PDF files, don't they?
If
Masamichi Hosoda writes:
> In addition, all fonts of the above without `-dgs-load-fonts' option are fine.
> I suggest removing `-dgs-load-fonts' option from lilypond-book.
> I think that `--bigpdfs' option is more suitable than
> `-dgs-load-fonts'.
Either make for particularly large PDF files, d
> As of
> http://www.mail-archive.com/bug-lilypond@gnu.org/msg40846.html
> I had uninstalled Noto and instead installed IPA fonts _and_ IPAex fonts.
> After uninstalling IPAex fonts - first the test-case worked and now I
> have success on a full `make doc'.
It seems that fonts-ipaexfont-{mincho|go
2016-06-04 15:12 GMT+02:00 Masamichi Hosoda :
>> In addition, the following command sequence succeeds:
>>
>> lilypond-book aaa-lilybook-test.lytex
>> latex aaa-lilybook-test.tex
>> dvips aaa-lilybook-test.dvi
>> ps2pdf aaa-lilybook-test.ps
>> evince aaa-lilybook-test.pdf
>>
>> aaa-lilybook-test.ps
> In addition, the following command sequence succeeds:
>
> lilypond-book aaa-lilybook-test.lytex
> latex aaa-lilybook-test.tex
> dvips aaa-lilybook-test.dvi
> ps2pdf aaa-lilybook-test.ps
> evince aaa-lilybook-test.pdf
>
> aaa-lilybook-test.ps is >16MB again, though.
Thank you for your results.
2016-06-03 23:57 GMT+02:00 Thomas Morley :
> 2016-06-03 14:02 GMT+02:00 Masamichi Hosoda :
>>> %%% start of aaa-lilybook.lytex
>>>
>>> \documentclass[a4paper]{article}
>>>
>>> \begin{document}
>>>
>>> \begin{lilypond}
>>> \markup {
>>> %foo bar buzz
>>> いろはにほへど ちりぬるを
>>> }
>>>
>>> \end{lily
2016-06-03 14:02 GMT+02:00 Masamichi Hosoda :
>> %%% start of aaa-lilybook.lytex
>>
>> \documentclass[a4paper]{article}
>>
>> \begin{document}
>>
>> \begin{lilypond}
>> \markup {
>> %foo bar buzz
>> いろはにほへど ちりぬるを
>> }
>>
>> \end{lilypond}
>>
>> \end{document}
>>
>> %%% end of aaa-lilybo
> %%% start of aaa-lilybook.lytex
>
> \documentclass[a4paper]{article}
>
> \begin{document}
>
> \begin{lilypond}
> \markup {
> %foo bar buzz
> いろはにほへど ちりぬるを
> }
>
> \end{lilypond}
>
> \end{document}
>
> %%% end of aaa-lilybook.lytex
>
> always fails with:
>
> $ lilypond-book --o
Thomas Morley writes:
> First the good news.
> With a build from a checkout of recent staging, I can successfully run
> make LANGS='' doc
> without any failure for orchestra.ly
> ... as soon as I comment/delete all japanese !!
Yes, it was pretty obvious that we are talking about two separate
pro
>> Hmm, pdflatex... What happens if you enforce xelatex?
>
> $ lilypond-book --latex-program=xelatex --output=out --pdf \
>aaa-lilybook.lytex
> [...]
> fatal error: failed files: "28/lily-a7047c84.ly"
OK. What Japanese font is used in the lilypond-book example? Is it
the same
2016-06-02 23:19 GMT+02:00 Werner LEMBERG :
>
>> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default
>> page settings.
>
> Hmm, pdflatex... What happens if you enforce xelatex?
$ lilypond-book --latex-program=xelatex --output=out --pdf aaa-lilybook.lytex
lilypond-book (GNU LilyPond
> Running `pdflatex' on file `/tmp/tmpP_qJ7Q.tex' to detect default
> page settings.
Hmm, pdflatex... What happens if you enforce xelatex?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilyp
LilyPond can be very finicky trying to get a clean build. That's why we
recommend using LilyDev.
I realize this is not a great answer for a Linux hacker.
I've looked briefly through your logs. Are you running a multi-processor
build (make -j3 doc)? If so, that can make it harder to interpret
On 16-03-2016 21:42, James wrote:
No 'configure' output?
Oh yes; attached.
What happens of you run
Apt-get builddep Lilypond?
Does it list any packages that you haven't installed.
apt-get build-dep lilypond
found five fonts, but nothing else. Unfortunately the installation of
these has n
Villum,
On 09/03/16 11:02, Villum Sejersen wrote:
- Original Message - From: "Villum Sejersen"
To: Sent: Wednesday, March 09, 2016 9:52 AM Subject:
make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from
latest git
- Original Message - From: "Villum Sejersen"
To: Sent: Wednesday, March 09, 2016 9:52 AM Subject:
make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from
latest git sources, make doc does not compile the 2.19.38 vers
Villum Sejersen writes:
> While make [all] and make install repeatably works as usual from
> latest git sources, make doc does not compile the 2.19.38 version,
> regardless how many, how many times and which cleaning attempts I try
> before.
>
> Tanks in advance for any advice...
sudo apt-get in
- Original Message -
From: "Villum Sejersen"
To:
Sent: Wednesday, March 09, 2016 9:52 AM
Subject: make doc fails after updating dev to VERSION 2.19.38
While make [all] and make install repeatably works as usual from latest
git sources, make doc does not compile the 2.19.38 version, r
Il giorno sab 1 nov 2014 alle 12:18, David Kastrup ha
scritto:
Probably not related, but some days ago I changed default TMPDIR
(/tmp) to save some space on / partition:
$ echo $TMPDIR
/home/fede/.cache
It looks to me like .cache starts with a dot...
Ok, the easiest fix was changing TMP
Federico Bruni writes:
> 'make doc' is returning the error below, can you help me?
>
> make[2]: Entering directory '/home/fede/lilypond-git/Documentation'
> BSTINPUTS=./essay /home/fede/lilypond-git/scripts/build/out/bib2texi \
> -s /home/fede/lilypond-git/Documentation/lily-bib \
> -o ./out-www/
- Original Message -
From: "Urs Liska"
To: "LilyPond Development Team"
Sent: Saturday, January 04, 2014 8:04 AM
Subject: Make doc - English only?
Is there a way to make doc without transltations?
When working on the website I use
make WEB_LANGS='' website, but is there an equivalent
Keith OHara writes:
> Phil Holmes philholmes.net> writes:
>
>> Processing `Documentation/ly-examples/orchestra.ly'
>> Parsing...
>> Interpreting music...
>> Preprocessing graphical objects...Segmentation fault
>>
>> Because it only happens on make doc (I can't reproduce it directly) until
>> t
Phil Holmes philholmes.net> writes:
> Processing `Documentation/ly-examples/orchestra.ly'
> Parsing...
> Interpreting music...
> Preprocessing graphical objects...Segmentation fault
>
> Because it only happens on make doc (I can't reproduce it directly) until
> today I'd not spent the time tryi
- Original Message -
From: "David Kastrup"
To:
Sent: Saturday, June 22, 2013 5:28 PM
Subject: Re: Make doc crashing on my PC
"Phil Holmes" writes:
For a while, I've been struggling to get make doc working consistently
on my build PC. This has been seen w
"Phil Holmes" writes:
> For a while, I've been struggling to get make doc working consistently
> on my build PC. This has been seen with my patchy failing, as well.
> I consistently get this in the error log:
>
> Changing working directory to: `./out-www'
> Processing `/home/phil/lilypond-git/Do
: David Nalesnik
To: Julien Rioux
Cc: LilyPond Devel
Sent: Sunday, March 17, 2013 2:17 AM
Subject: Re: make doc fails
Julien,
On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux wrote:
On 16/03/2013 6:27 PM, David Nalesnik wrote:
/usr/bin/python -tt
/home/david/lilypond
Julien,
On Sat, Mar 16, 2013 at 7:31 PM, Julien Rioux wrote:
> On 16/03/2013 6:27 PM, David Nalesnik wrote:
>
>> /usr/bin/python -tt
>> /home/david/lilypond-git/**scripts/build/create-weblinks-**itexi.py >
>> out-www/weblinks.itexi
>> make[3]: *** No rule to make target
>> `/home/david/lilypond-
On 16/03/2013 6:27 PM, David Nalesnik wrote:
/usr/bin/python -tt
/home/david/lilypond-git/scripts/build/create-weblinks-itexi.py >
out-www/weblinks.itexi
make[3]: *** No rule to make target
`/home/david/lilypond-git/Documentation/cs/web/news-front.itexi', needed by
`out-www/web.texi'. Stop.
Tr
- Original Message -
From: "Jean-Charles Malahieude"
To: "Phil Holmes"
Cc: ; "David Kastrup"
Sent: Saturday, February 02, 2013 5:30 PM
Subject: Re: Make doc; create-weblinks and translations
Le 29/01/2013 17:20, Phil Holmes disait :
- Original Mess
Le 29/01/2013 17:20, Phil Holmes disait :
- Original Message - From: "David Kastrup"
To:
Sent: Tuesday, January 29, 2013 4:13 PM
Subject: Re: Make doc; create-weblinks and translations
"Phil Holmes" writes:
As for getting rid of unmaintained output - I a
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 29, 2013 4:13 PM
Subject: Re: Make doc; create-weblinks and translations
"Phil Holmes" writes:
As for getting rid of unmaintained output - I agree on balance. It
would be interest
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Tuesday, January 29, 2013 3:56 PM
> Subject: Re: Make doc; create-weblinks and translations
>
>
>> "Phil Holmes" writes:
>
>> I
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, January 29, 2013 3:56 PM
Subject: Re: Make doc; create-weblinks and translations
"Phil Holmes" writes:
I noticed that a lot of half-translated Czech pages contain a lot of
stuff from the _German_
"Phil Holmes" writes:
> 1. No Czech translations means lots of error messages (which could
> obscure ones
> we actually want to see, in order to correct them).
> I plan to create a patch that will:
>
> a) Restore the -cs pages to use -en (default) "translations" thus
> getting rid of
> the error
Il 30/12/2012 09:06, Federico Bruni ha scritto:
I can't find any information about dblatex developers.
I'll send a bug report to Debian bug tracking system.
Ok, problem solved thanks to the Debian maintainer:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696976
The problem was the python pa
Federico Bruni writes:
> Il 29/12/2012 17:05, Federico Bruni ha scritto:
>> Il 29/12/2012 16:51, David Kastrup ha scritto:
>>> I have no idea, but an incomplete installation of dblatex or one that is
>>> unable to find its own parts seems plausible.
>>
>> The file which contains TexModule is plug
Il 29/12/2012 17:05, Federico Bruni ha scritto:
Il 29/12/2012 16:51, David Kastrup ha scritto:
I have no idea, but an incomplete installation of dblatex or one that is
unable to find its own parts seems plausible.
The file which contains TexModule is plugins.py
I have that file both under pyth
Il 29/12/2012 16:51, David Kastrup ha scritto:
I have no idea, but an incomplete installation of dblatex or one that is
unable to find its own parts seems plausible.
The file which contains TexModule is plugins.py
I have that file both under python2.6 and python2.7
This is what I get:
# grep
"Phil Holmes" writes:
>> Error: cannot import name TexModule
>>
>> --
>> David Kastrup
>
>
> Yes - sorry - didn't see the attachment. So - what might cause this
> error?
grep TexModule `dpkg -L dblatex` 2>/dev/null
/usr/share/pyshared/dbtexmf/dblatex/grubber/xetex.py:from plugins import
TexMo
- Original Message -
From: "David Kastrup"
To:
Sent: Saturday, December 29, 2012 2:32 PM
Subject: Re: make doc: cannot import name TexModule (but dblatex is now
arequireddependency)
"Phil Holmes" writes:
- Original Message -
From: "Federico Brun
1 - 100 of 248 matches
Mail list logo
