> Thanks, Werner, for the suggestion. I just tried it, and lilypond still
> errors as before.
Of all the errors you posted, which one is it now?
On 2023-05-18 22:09, Werner LEMBERG wrote:
ran make successfully, got carried away and may have shot myself in
the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Thanks,
> ran make successfully, got carried away and may have shot myself in
> the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Werner
On 2023-05-18 21:07, Colin Campbell wrote:
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory
and start a fresh build.
Deleted /build,
mkdir build,
cd build
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
Deleted /build,
mkdir build,
cd build
ran make successfully, got carried away and may
Wonderful, thank you!
\--
Gwyn Ciesla
she/her/hers
\
in your fear, seek only peace
in your fear, seek only love
\-d. bowie
Sent from Proton Mail mobile
\ Original Message
On May 18, 2023, 12:53 PM, Jean Abou
Le jeudi 18 mai 2023 à 11:27 +0200, Jean Abou Samra a écrit :
> Gwyn, is it convenient for you to test patches? I think I see what this is
> caused by, but I cannot reproduce the bug in a local build (knowing what
> exact compiler flags are used in Fedora's builds
> might help).
> I'd like to kno
Gwyn, is it convenient for you to test patches? I think I see what this is
caused by, but I cannot reproduce the bug in a local build (knowing what exact
compiler flags are used in Fedora's builds might help).
I'd like to know if this fixes it:
```
diff --git a/lily/all-font-metrics-scheme.cc b
> I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
> Le 18 mai 2023 à 05:49, Colin Campbell a écrit :
>
> Attached console output. I'll do a git pull and recompile a bit later, and
> report what happens. Note that the same test file when compiled using
> Frescobaldi as a front end, produces the following output:
>
>
> Starting lilypond 2.
10 matches
Mail list logo
