Re: Compiling on ish

[Ben Bradshaw]

Well I thought I would report back for posterity in case anyone else runs into the same problem. I was working on the tests for fontforge and one failed because I didn't have some python module installed that it needed. I installed that and then recompiled fontforge with every extra thing enabled that I could. That seems to have solved the problem and I was able to compile the rest of lilypond!

Thanks again for help in pointing to where the problem was,

Best,

Ben

On Mon, Aug 26, 2024 at 8:01 AM Werner LEMBERG <wl@gnu.org> wrote:

> So I turned on FONTFORGE_VERBOSE and ran the same script. It shows
> the same warning about Mac Roman, but then continues, which was
> encouraging. It then runs four lines:
>
> Select all();
> RemoveOverlap();
> AddExtrema();
> Simplify(0, 2);
>
> Then nothing happens. I don't actually get any error messages. Is
> this just a script that will take a very long time to run?

No, it should finish within a fraction of a second.

You should search and, in case of nothing pops up, submit a FontForge
issue at

  https://github.com/fontforge/fontforge/issues

to get more help.  Be as detailed as possible, i.e., describe your OS,
your build environment, the building tools, the command-line for
configuring FontForge, provide logging for both configuration and
compilation, provide an input file, the exact command-line that
triggers the problematic behaviour, etc., etc.

You could also try older versions of FontForge to check whether a bug
has been introduced recently, or whether it never worked for your
combo of OS and tools.


    Werner