New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest fontforge (20170731) segfaults when running ricty_generator #49

Closed
aikinai opened this Issue Aug 1, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@aikinai
Collaborator

aikinai commented Aug 1, 2017

I'm getting this error when I try to install Ricty today:

./ricty_generator-4.1.0.sh: line 1042: 67291 Segmentation fault: 11  $fontforge_command -script ${tmpdir}/${ricty_generator} 2> $redirection_stderr

It seems to be a bug in the latest Fontforge, so I manually reverted to the previous version of Fontforge with brew edit fontforge (just copied and pasted the old formula). It's very hacky and I don't know if it's even possible to add this officially to the Ricty formula, but I just wanted to share the hacky solution here in case other people run into the same issue.

@sanemat

This comment has been minimized.

Show comment
Hide comment
@sanemat

sanemat Aug 1, 2017

Owner

Segmentation fault 😿
Thank you for sharing.

Owner

sanemat commented Aug 1, 2017

Segmentation fault 😿
Thank you for sharing.

@equal-l2

This comment has been minimized.

Show comment
Hide comment
@equal-l2

equal-l2 Aug 2, 2017

Collaborator

This issue occurs only with Homebrew fontforge.
In other word, you can successfully build with official build of fontforge.

Collaborator

equal-l2 commented Aug 2, 2017

This issue occurs only with Homebrew fontforge.
In other word, you can successfully build with official build of fontforge.

@equal-l2

This comment has been minimized.

Show comment
Hide comment
@equal-l2

equal-l2 Sep 14, 2017

Collaborator

The issue seems to have been solved by Homebrew/homebrew-core#17845.
Feel free to reopen if it still occurs.

Collaborator

equal-l2 commented Sep 14, 2017

The issue seems to have been solved by Homebrew/homebrew-core#17845.
Feel free to reopen if it still occurs.

@equal-l2 equal-l2 closed this Sep 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment