Re: Build problem with fonts

2019-12-09 Thread Federico Bruni
Il giorno lun 9 dic 2019 alle 11:18, Federico Bruni ha scritto: Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha scritto: Your `t1asm` binary crashes with a segmentation fault, as can be seen in last two lines of `mf2pt1.strace.657213`: --- SIGSEGV {si_signo=SIGSEGV,

Re: Build problem with fonts

2019-12-09 Thread Federico Bruni
Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG ha scritto: Your `t1asm` binary crashes with a segmentation fault, as can be seen in last two lines of `mf2pt1.strace.657213`: --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x3055683} --- +++ killed by SIGSEGV (core

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
>> Please try again with >>strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf >> so that we can see the strace messages from `t1asm` also. Note that >> you will get at least two files called `mf2pt1.strace.X`, where >> `X` is a process ID. >> > > Four log-files were created, and the 3

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 18:12, Werner LEMBERG a écrit : Please try again with strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf so that we can see the strace messages from `t1asm` also. Note that you will get at least two files called `mf2pt1.strace.X`, where `X` is a process ID. Four

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
>> Strange indeed. Can you temporarily replace `mf2pt1` with a script >> that calls `strace`? Something like >>strace mf2pt1 ... &> ~/mf2pt1.strace.log >> You could then investigate in more detail which files `mf2pt1` tries >> to open and/or execute. >> > > [jcharles@pc1 mf]$ strace

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 17:10, Werner LEMBERG a écrit : Strange indeed. Can you temporarily replace `mf2pt1` with a script that calls `strace`? Something like strace mf2pt1 ... &> ~/mf2pt1.strace.log You could then investigate in more detail which files `mf2pt1` tries to open and/or execute.

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
> which t1asm > /usr/bin/t1asm > > so I don't see any reason why, just at once, it failed at running… > after a good sleeping night! Strange indeed. Can you temporarily replace `mf2pt1` with a script that calls `strace`? Something like strace mf2pt1 ... &> ~/mf2pt1.strace.log You could

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Le 08/12/2019 à 16:51, Werner LEMBERG a écrit : Can you execute t1asm? t1asm --help It works either in $HOME or in my compiling folders. Is it in your path that you use for compiling lilypond? which t1asm /usr/bin/t1asm so I don't see any reason why, just at once, it failed at

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG
> I notice, upwards in the log, that > > Invoking "t1asm feta11.pt1 feta11.pfb"... > mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find > another way to convert feta11.pt1 to feta11.pfb > > > despite I've t1utils-1.41-1.fc31.x86_64 installed. Can you execute t1asm?

Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude
Hi all, For about two weeks now, I'm unable to build and then merge translation with stable, even after a fresh clone. I cannot believe it has something to do with an upgrade from Fedora 30 to 31. Tail of the log : --8<-- cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe Copyright