Folks,
Carl wrote to me privately:
> OK, so now I have a failure:
>
> I did
>
> ```
> rm -rf build
> mkdir build
> cd build
> ../autogen.sh --currdir
> ../configure &> configure.log
> make -j10 CPU_COUNT=10 all
> make doc LANGS="en" VERBOSE=1 CPU_COUNT=10 -j10 &> make.doc.log
> ```
> And the m
> I can confirm that I get the proper HTML pages, compiling with -j10
> on both make bytecode and make doc.
Great!
> It was delightful to see the proper lilypond website on my local
> file system! Thank you so much for fixing this!
Glad that I could help. I will now polish the MR as requested
On Mon, Feb 12, 2024 at 9:22 AM Werner LEMBERG wrote:
>
> v2.25.13-8-gbe52228a70
>
> Please test again! Theoretically, you should now get proper HTML
> pages.
>
I can confirm that I get the proper HTML pages, compiling with -j10 on both
make bytecode and make doc.
It was delightful to see th
On Sat, Feb 10, 2024 at 7:20 AM Werner LEMBERG wrote:
>
> >> systems like macOS that neither have or use '/bin/bash'.
> >
> > Apple changed the default shell for new users to zsh about 5 years
> > ago, but bash is still there. I don't oppose making the build
> > scripts more portable, but let's
>> systems like macOS that neither have or use '/bin/bash'.
>
> Apple changed the default shell for new users to zsh about 5 years
> ago, but bash is still there. I don't oppose making the build
> scripts more portable, but let's not misunderstand the situation.
OK, thanks – let's see whether t
On 2024-02-10 07:52, Werner LEMBERG wrote:
systems like macOS that neither have or use '/bin/bash'.
Apple changed the default shell for new users to zsh about 5 years ago,
but bash is still there. I don't oppose making the build scripts more
portable, but let's not misunderstand the situati
>> If I click on the Notation link from that page, I get to:
>>
>> out-www/offline-root/Documentation/web/notation.html
>>
>> which has no css, but has lots of links.
>
> This shouldn't happen, and it means that your documentation build is
> still not correct.
Continuing with the analysis of Car
> If I click on the Notation link from that page, I get to:
>
> out-www/offline-root/Documentation/web/notation.html
>
> which has no css, but has lots of links.
This shouldn't happen, and it means that your documentation build is
still not correct.
> I'm happy to send a tar file of my offlin
> "/Users/carl/Development/lilypond/build/out/lybook-db/
> snippet-names-c5b165525229969dd268a5b19f9f64fd.ly"' returned
> non-zero exit status 1.
Please try to find out which of the snippet files mentioned in the
above file failed. `*.log` files should be in directory
`out/lybook-db`, too, and
On Sun, Feb 4, 2024 at 7:21 AM Werner LEMBERG wrote:
>
>
> Please test
>
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2254
>
> It should fix all the build problems you've reported.
>
This merge request allowed me to build the documentation using MacOS cp and
find.
I still got error
On Sat, Feb 3, 2024 at 12:01 AM Werner LEMBERG wrote:
>
> [Carl sent me the file listing off-list, thanks! I will analyze it in
> due course.]
>
> > [...] and make test with a single job (to avoid race conditions that
> > have given me trouble in the past):
>
> Interesting. When is the 'past'?
>> > I omitted the '-l' option in the cp calls in the patch.
>> >
>> > 'make doc' succeeded without any errors, so I thought I had success. But
>> > it turns out that
>> >
>> > a) I appear not to have the .css files copied (at least the output
>> >showed no css -- just basic white screen), a
[Carl sent me the file listing off-list, thanks! I will analyze it in
due course.]
> [...] and make test with a single job (to avoid race conditions that
> have given me trouble in the past):
Interesting. When is the 'past'? This shouldn't happen today, and it
would be great if you could try
On Fri, Feb 2, 2024 at 4:34 AM Werner LEMBERG wrote:
> >> Please read this and check whether you are affected by this
> >> problem. In case you can confirm the issue please try whether it
> >> works if you omit the `-l` option in all `cp` calls in my patch.
> >
> > I checked -- the results of th
>> Please read this and check whether you are affected by this
>> problem. In case you can confirm the issue please try whether it
>> works if you omit the `-l` option in all `cp` calls in my patch.
>
> I checked -- the results of the problem were different for me than
> for the bug report. I got
On Thu, Feb 1, 2024 at 10:47 AM Werner LEMBERG wrote:
>
>
> Doing a bit of an internet search it seems this is a bug in the `cp`
> implementation on macOS (as unbelievable it may be, given that `cp` is
> such a fundamental command that exists since decades):
>
>
> https://apple.stackexchange.com/
> 'make doc' failed.
>
> It appears that under some conditions, we end up with a path
> including '//'.
Multiple slashes in succession are completely harmless; they are
simply equivalent to `/`.
Doing a bit of an internet search it seems this is a bug in the `cp`
implementation on macOS (as un
On Wed, Jan 31, 2024 at 10:53 PM Werner LEMBERG wrote:
>
>
> Thanks a lot, very helpful. Please apply the attached patch to the
> top-level `GNUmakefile.in` file, then retry from scratch (including
> the `configure` step); it should catch all of the three problems
> you've encountered.
>
It see
> I've attached three compressed log files. [...]
Thanks a lot, very helpful. Please apply the attached patch to the
top-level `GNUmakefile.in` file, then retry from scratch (including
the `configure` step); it should catch all of the three problems
you've encountered.
The `-maxdepth` and `-mi
On Wed, Jan 31, 2024 at 12:49 AM Werner LEMBERG wrote:
>
> > I already had to install (via homebrew) gnu coreutils and gnu
> > findutils, since the MacOS 'cp' and 'find' commands don't work the
> > same as the respective GNU commands.
>
> Please give more details. What problems did you experienc
> I already had to install (via homebrew) gnu coreutils and gnu
> findutils, since the MacOS 'cp' and 'find' commands don't work the
> same as the respective GNU commands.
Please give more details. What problems did you experience with `cp`
and `find`? Did this happen during a call to `make ..
Still trying to get 'make doc' to complete successfully.
At this point, I think I'm through all the lilypond stuff, and now I'm
stuck in shell script errors.
I already had to install (via homebrew) gnu coreutils and gnu findutils,
since the MacOS 'cp' and 'find' commands don't work the same as th
>> Aah, this looks like a bug in `typography-demo.ly`. Please try the
>> following line in `typography-demo.ly` instead of the three
>> original font lines.
>>
>> ```
>> property-defaults.fonts.serif = "Linux Libertine O, Noto Serif CJK JP, Noto
>> Serif JP, serif"
>> ```
>
> I can confirm that
On Wed, Jan 24, 2024 at 11:49 PM Werner LEMBERG wrote:
>
> >> I installed Noto Serif JP, and added it to the fontcofig cache.
> >> That got me through the previous file error. But then I got
> >> stopped on another Japanese font (I suppose this might be a Linux
> >> Libertine font, but my fc-lis
>> I installed Noto Serif JP, and added it to the fontcofig cache.
>> That got me through the previous file error. But then I got
>> stopped on another Japanese font (I suppose this might be a Linux
>> Libertine font, but my fc-list command shows that I have them
>> installed):
Interesting. Th
On Tue, Jan 23, 2024 at 4:54 AM Carl Sorensen
wrote:
>
>
> On Mon, Jan 22, 2024 at 8:37 PM Carl Sorensen
> wrote:
>
>>
>>
>> On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra
>> wrote:
>>
>>> Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
>>> > > Looks like no error:
>>> > >
>>>
> carl@Carls-MBP-2 lilypond % tidy --version
>
> HTML Tidy for Mac OS X released on 31 October 2006 - Apple Inc. build 6141
This explains the failure, thanks: Your `tidy` version doesn't support
HTML 5. I've submitted an MR to catch this.
https://gitlab.com/lilypond/lilypond/-/merge_request
On Mon, Jan 22, 2024 at 8:37 PM Carl Sorensen
wrote:
>
>
> On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra
> wrote:
>
>> Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
>> > > Looks like no error:
>> > >
>> > > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond input/regression/
>> Can someone remind me why the build system sets the C locale in the
>> first place?
>
> Answering my own question: I guess it is because we can't assume the
> system has an en_US.UTF-8 locale or a C.UTF-8 locale?
Exactly. Some time ago (see
https://lists.gnu.org/archive/html/lilypond-devel/2
On Mon, Jan 22, 2024 at 5:58 PM Jean Abou Samra wrote:
> Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
> > > Looks like no error:
> > >
> > > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond input/regression/
> pdf-copy-paste.ly
> > > GNU LilyPond 2.25.13 (running Guile 3.0)
>
> Can someone remind me why the build system sets the C locale
> in the first place?
Answering my own question: I guess it is because we can't assume the
system has an en_US.UTF-8 locale or a C.UTF-8 locale?
Maybe we ought to set only LC_MESSAGES to C? It should prevent overriding
the system loc
Ah, but, wait.
$ touch àéù.txt
$ guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
$1 = #
~/tmp $ LC_ALL=C guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure open-file: No such file or directory: "??.txt"
OK,
Le lundi 22 janvier 2024 à 18:00 -0700, Carl Sorensen a écrit :
> So I ran the file in this log message:
>
>
> carl@carls-mbp-2 build % out/bin/lilypond out/share/lilypond/current/ly/
> init.ly
>
> GNU LilyPond 2.25.13 (running Guile 3.0)
>
> Processing `out/share/lilypond/current/ly/init.ly'
>
Le mardi 23 janvier 2024 à 01:58 +0100, Jean Abou Samra a écrit :
> The latter is basically that this regtest (pdf-copy-paste.ly)
> has Japanese text, specifying the Noto Serif JP font, but since
> you apparently don't have that font installed, Fontconfig falls
> back to some system font, and appar
On Mon, Jan 22, 2024 at 4:37 PM Carl Sorensen
wrote:
>
>
> On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote:
>
>>
>> >> You have to check the log files in `lybook-db` to find the problematic
>> >> `.ly` file(s). Does `make test` succeed? You should actually try that
>> >> before running `
Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
> > Looks like no error:
> >
> > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond
> > input/regression/pdf-copy-paste.ly
> > GNU LilyPond 2.25.13 (running Guile 3.0)
> > Processing `input/regression/pdf-copy-paste.ly'
> > Parsing..
On Mon, Jan 22, 2024 at 3:58 PM Jean Abou Samra wrote:
> Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit :
> > > >
> > OK, thanks. This means that there is apparently a macOS-specific
> > problem with either Guile or LilyPond. For testing purposes I renamed
> > one of my local fo
On Sun, Jan 21, 2024 at 12:33 AM Werner LEMBERG wrote:
>
> >> You have to check the log files in `lybook-db` to find the problematic
> >> `.ly` file(s). Does `make test` succeed? You should actually try that
> >> before running `make doc`...
> >>
> >
> > Interesting -- the CG has make doc show
Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit :
> > >
> OK, thanks. This means that there is apparently a macOS-specific
> problem with either Guile or LilyPond. For testing purposes I renamed
> one of my local fonts to something containing Katakana, and my
> self-compiled LilyP
>> > In procedure open-file: No such file or directory:
>> > "/System/Library/Fonts/??? W4.ttc" [...]
>> >
>> > SO it looks to me like there's a problem with not getting UTF characters
>> > into the proper file name in the Scheme procedure. Any ideas for what to
>> > do next?
>>
>> What d
On Sun, Jan 21, 2024 at 11:05 PM Werner LEMBERG wrote:
> > In procedure open-file: No such file or directory:
> > "/System/Library/Fonts/??? W4.ttc"
> >
> > I checked out the /System/Library/Fonts directory, and found these fonts
> > listed:
> >
> > ヒラギノ角ゴシック W3.ttc
> >
> > ヒラギノ角ゴシック
> In procedure open-file: No such file or directory:
> "/System/Library/Fonts/??? W4.ttc"
>
> I checked out the /System/Library/Fonts directory, and found these fonts
> listed:
>
> ヒラギノ角ゴシック W3.ttc
>
> ヒラギノ角ゴシック W4.ttc
>
> SO it looks to me like there's a problem with not getting UTF ch
Thanks for the hint, Dan!
I got to a new log file that gave me what I believe is a helpful error
message:
carl@carls-mbp-2 build % cat out/lybook-testdb/0f/lily-acefd898.log
Processing `0f/lily-acefd898.ly'
Parsing...
Renaming input to: `/Users/carl/Development/lilypond/input/regression/
pdf-c
>> You have to check the log files in `lybook-db` to find the problematic
>> `.ly` file(s). Does `make test` succeed? You should actually try that
>> before running `make doc`...
>>
>
> Interesting -- the CG has make doc show up before make test. But I
> appreciate the suggestion, so I decided
On 2024-01-20 20:55, Carl Sorensen wrote:
File
"/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py",
line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/tidy', '-o',
'/dev/null', '-q', 'compare
On Thu, Jan 18, 2024 at 11:05 PM Werner LEMBERG wrote:
>
> > "/Users/carl/Development/lilypond/build/out/lybook-db/
> > snippet-names-ece0c512da6daf7d9aff45809ce97556.ly"' returned non-zero
> exit
> > status 1.
>
> You have to check the log files in `lybook-db` to find the problematic
> `.ly` fil
> "/Users/carl/Development/lilypond/build/out/lybook-db/
> snippet-names-ece0c512da6daf7d9aff45809ce97556.ly"' returned non-zero exit
> status 1.
You have to check the log files in `lybook-db` to find the problematic
`.ly` file(s). Does `make test` succeed? You should actually try that
before
47 matches
Mail list logo