This repository has been archived by the owner. It is now read-only.

Lilypond 2.16 failed to install on 10.6.8 (missing WOFF font) #15437

Closed
egilbert opened this Issue Oct 13, 2012 · 12 comments

Comments

Projects
None yet
4 participants
@egilbert

I’m trying to upgrade Lilypond from 2.14.2 to 2.16 on Mac OS X 10.6.8, but the installation stage fails, claiming the file ./out/emmentaler-11.woff is missing. This seems related to the second part of issue 3075.

TeX is installed (MacTeX 2012), fontforge is up-to-date. Details and complete log can be found here.

$ brew upgrade lilypond
==> Upgrading lilypond
==> Downloading http://download.linuxaudio.org/lilypond/sources/v2.16/lilypond-2
Already downloaded: /Users/user/Library/Caches/Homebrew/lilypond-2.16.0.tar.gz
==> ./configure --prefix=/usr/local/Cellar/lilypond/2.16.0 --enable-rpath --with
==> make all
==> make install
  File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/shutil.py", line 52, in copyfile
    fsrc = open(src, 'rb')
IOError: [Errno 2] No such file or directory: './out/emmentaler-11.woff'
make[1]: *** [local-install-outfiles] Error 1
make: *** [install] Error 2

Error: lilypond did not build
Logs: /Users/user/Library/Logs/Homebrew/lilypond/
Help: https://github.com/mxcl/homebrew/wiki/troubleshooting
@2bits

This comment has been minimized.

Show comment Hide comment
@2bits

2bits Oct 14, 2012

Contributor

Please try this

brew rm -f fontforge lilypond
brew update
brew prune
brew install --with-x --with-cairo fontforge
brew install lilypond

and let us know how it goes.

Contributor

2bits commented Oct 14, 2012

Please try this

brew rm -f fontforge lilypond
brew update
brew prune
brew install --with-x --with-cairo fontforge
brew install lilypond

and let us know how it goes.

@egilbert

This comment has been minimized.

Show comment Hide comment
@egilbert

egilbert Oct 15, 2012

Installation went fine with the --with-x --with-cairooptions. I haven’t tried typesetting any document yet.

Installation went fine with the --with-x --with-cairooptions. I haven’t tried typesetting any document yet.

@2bits

This comment has been minimized.

Show comment Hide comment
@2bits

2bits Oct 15, 2012

Contributor

Hey that's good news. It's a complex program. Please let us know how it goes and whether something needs tweaking. For instance, you may need or want pango support in fontforge which is an option I didn't bother to add in order to keep the variables low. That brings in freetype which lilypond might need. Thanks for your help.

Contributor

2bits commented Oct 15, 2012

Hey that's good news. It's a complex program. Please let us know how it goes and whether something needs tweaking. For instance, you may need or want pango support in fontforge which is an option I didn't bother to add in order to keep the variables low. That brings in freetype which lilypond might need. Thanks for your help.

@adamv

This comment has been minimized.

Show comment Hide comment
@adamv

adamv Oct 21, 2012

Contributor

Closing since original poster's problem was resolved.

Contributor

adamv commented Oct 21, 2012

Closing since original poster's problem was resolved.

@adamv adamv closed this Oct 21, 2012

@egilbert

This comment has been minimized.

Show comment Hide comment
@egilbert

egilbert Oct 28, 2012

Actually, while this is a perfectly good workaround, brew install lilypond still fails.

Actually, while this is a perfectly good workaround, brew install lilypond still fails.

@adamv adamv reopened this Oct 28, 2012

@2bits

This comment has been minimized.

Show comment Hide comment
@2bits

2bits Oct 29, 2012

Contributor

@egilbert You can't install lilypond, even though you fixed fontforge? Please gist the entire output of

HOMEBREW_MAKE_JOBS=1 VERBOSE=1 brew install lilypond

so we can see what it going wrong. Thanks.

Contributor

2bits commented Oct 29, 2012

@egilbert You can't install lilypond, even though you fixed fontforge? Please gist the entire output of

HOMEBREW_MAKE_JOBS=1 VERBOSE=1 brew install lilypond

so we can see what it going wrong. Thanks.

@egilbert

This comment has been minimized.

Show comment Hide comment
@egilbert

egilbert Oct 29, 2012

My bad, that wasn’t clear at all.

If I remove fontforge, then brew install lilypondstill doesn’t work. Although I haven’t tested it, I expect brew install lilypond to fail on a fresh install. I.e. that’s a workaround, it works fine with me, but the bug isn’t fixed. It thus seems weird to close the issue.

I could try and edit the fontforge formula to systematically add the required options, but I’m afraid that might break everything else. Or, possibly, bother fontforge users.

Then again, the regular updates of the softwares and the formulae might actually fix such bugs itself, making it useless to spend more time on the issue. In that case, sorry for having it reopened.

My bad, that wasn’t clear at all.

If I remove fontforge, then brew install lilypondstill doesn’t work. Although I haven’t tested it, I expect brew install lilypond to fail on a fresh install. I.e. that’s a workaround, it works fine with me, but the bug isn’t fixed. It thus seems weird to close the issue.

I could try and edit the fontforge formula to systematically add the required options, but I’m afraid that might break everything else. Or, possibly, bother fontforge users.

Then again, the regular updates of the softwares and the formulae might actually fix such bugs itself, making it useless to spend more time on the issue. In that case, sorry for having it reopened.

@2bits

This comment has been minimized.

Show comment Hide comment
@2bits

2bits Oct 29, 2012

Contributor

Yes that makes sense. It will be possible to make it fully automatic in maybe a month, when Jack's PR about formula dependencies and their options gets committed. Until then we can only put a "Requirement" into the lilypond formula that won't try to install it on 10.6.8 until you manually install fontforge with the specific options necessary.

Contributor

2bits commented Oct 29, 2012

Yes that makes sense. It will be possible to make it fully automatic in maybe a month, when Jack's PR about formula dependencies and their options gets committed. Until then we can only put a "Requirement" into the lilypond formula that won't try to install it on 10.6.8 until you manually install fontforge with the specific options necessary.

@adamv

This comment has been minimized.

Show comment Hide comment
@adamv

adamv Jan 7, 2013

Contributor

Someone please be explicit about how fontforge needs to be installed for lillypond to work, so I can put in a Requirement.

Thanks.

Contributor

adamv commented Jan 7, 2013

Someone please be explicit about how fontforge needs to be installed for lillypond to work, so I can put in a Requirement.

Thanks.

@adamv

This comment has been minimized.

Show comment Hide comment
@adamv

adamv Feb 3, 2013

Contributor

@jacknagel is depends_on 'fontforge' => ["with-x", "with-cairo"] the syntax we're looking for here?

Contributor

adamv commented Feb 3, 2013

@jacknagel is depends_on 'fontforge' => ["with-x", "with-cairo"] the syntax we're looking for here?

@jacknagel

This comment has been minimized.

Show comment Hide comment
@jacknagel

jacknagel Feb 3, 2013

Contributor

Yeah.

Contributor

jacknagel commented Feb 3, 2013

Yeah.

@adamv adamv closed this in f45d16c Feb 3, 2013

@adamv

This comment has been minimized.

Show comment Hide comment
@adamv

adamv Feb 3, 2013

Contributor

Added the dependencies. Note that both fontforge and lilypond are notoriously hard to build. Any new issues should be brought up in new tickets, though. After brew update you may want to remove all the deps, as there have been many gtk/pango/cairo updates since this was opened.

Contributor

adamv commented Feb 3, 2013

Added the dependencies. Note that both fontforge and lilypond are notoriously hard to build. Any new issues should be brought up in new tickets, though. After brew update you may want to remove all the deps, as there have been many gtk/pango/cairo updates since this was opened.

@xu-cheng xu-cheng locked and limited conversation to collaborators Feb 16, 2016

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