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, si_code=SEGV_MAPERR, 
si_addr=0x3055683} ---

  +++ killed by SIGSEGV (core dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.


Same here, I've reported the bug ten days ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1777987

Maintainer did not reply yet.
I'll see if I can send a patch when I have some time.





Jean-Charles, I sent a PR here:
https://src.fedoraproject.org/rpms/t1utils/pull-request/1


I've built a new RPM from that spec file and I can build lilypond again.
Find it attached (x86_64).




t1utils-1.41-2.fc31.x86_64.rpm
Description: application/rpm

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 dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.


Same here, I've reported the bug ten days ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1777987

Maintainer did not reply yet.
I'll see if I can send a patch when I have some time.

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 resulting font-files as well.

Thanks.

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 dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.

I use the `t1asm` binary from TeXLive 2019; it is works without
problems.


Werner

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 log-files were created, and the 3 resulting font-files as well.

feta11.pfb seems to be truncated, last lines being just

"
dup 142 /scripts.caesura.straight put
dup 1
"

And the console, as usual, finally spits

"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"


I enclose the generated files in mf/ if it helps.

Thanks,

ps. The dinner is smoothly cooking, just waiting for Madame to come home 
after concert.

--
Jean-Charles


mf2pt1.strace-ff.tar.xz
Description: application/xz


feta11.tar.xz
Description: application/xz

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 mf2pt1 feta11.mf &> ~/mf2pt1.strace
> 
> generates the .pfb .pt1 and .tfm

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.


   Werner

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.



[jcharles@pc1 mf]$ strace mf2pt1 feta11.mf &> ~/mf2pt1.strace

generates the .pfb .pt1 and .tfm

And I don't see anything special in the log (enclosed), at first glance 
since I'm not really able to interpret it.


Have to leave for now, and come back tomorrow.

TIA,
--
Jean-Charles


mf2pt1.strace.tar.xz
Description: application/xz

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 then investigate in more detail which files `mf2pt1` tries
to open and/or execute.


Werner

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 running… after 
a good sleeping night!


--
Jean-Charles

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?

  t1asm --help

Is it in your path that you use for compiling lilypond?


Werner

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 (c) 2000-2019. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later 

 with many parts BSD . Please read 
LICENSE.

 Version: 20190801
 Based on sources from 00:00 UTC 15-Aug-2019-ML-D.
Cannot open /home/jcharles/GIT/Stable/mf/out/feta11.pfb
The requested file, feta11.pfb, does not exist
MergeFonts: Can't find font: feta11.pfb
Called from...
 emmentaler-11.genpe: line 17
make[1]: *** [GNUmakefile:138: out/emmentaler-11.otf] Error 1
make[1]: Leaving directory '/home/jcharles/GIT/Stable/mf'
make: *** 
[/home/jcharles/GIT/Stable/stepmake/stepmake/generic-targets.make:6: 
all] Error 2


Compilation exited abnormally with code 2 at Sun Dec  8 15:46:09
-->8--

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.

Some hints?

Cheers,
--
Jean-Charles