Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-25 Thread Gabriel Striewe
On Fri, Oct 24, 2014 at 02:20:38AM +0200, Gabriel Striewe wrote: You may have to update to Command Line Tools (OS X 10.10) [1]. 1. https://developer.apple.com/downloads/index.action?name=for%20Xcode%20- Unfortunately, that was not the reason; the Command Line Tools are up to date.

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-25 Thread Paul Morris
linux wrote So Mac Os X Yosemite 10.10 with updated Xcode and Command Line Tools (6.1) is without lilypond for the moment! Well, only if you are trying to install LilyPond with homebrew, right? You can still download and install LilyPond from here, and it should work fine:

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-23 Thread Hans Aberg
On 22 Oct 2014, at 18:40, Gabriel Striewe li...@gabriel-striewe.de wrote: On Wed, Oct 22, 2014 at 06:49:21PM +0300, Omer Katzir wrote: I actually have a problem, I can't compile the files, no error, just not doing it. I'm not sure if it's my very old machine or the upgrade. Me, too, am

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-23 Thread Gabriel Striewe
You may have to update to Command Line Tools (OS X 10.10) [1]. 1. https://developer.apple.com/downloads/index.action?name=for%20Xcode%20- Unfortunately, that was not the reason; the Command Line Tools are up to date. I am having a discussion on the homebrew mailing list just now...

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-22 Thread Omer Katzir
I actually have a problem, I can't compile the files, no error, just not doing it. I'm not sure if it's my very old machine or the upgrade. On Wed, Oct 22, 2014 at 2:51 AM, Paul Morris p...@paulwmorris.com wrote: Thanks for the info everyone. I've upgraded and LilyPond and Frescobaldi are

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-22 Thread Gabriel Striewe
On Wed, Oct 22, 2014 at 06:49:21PM +0300, Omer Katzir wrote: I actually have a problem, I can't compile the files, no error, just not doing it. I'm not sure if it's my very old machine or the upgrade. Me, too, am having problems compiling lilypond (2.18.2) with homebrew. I filed a bug on

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Thomas Scharkowski
Same here. Original-Nachricht i have upgraded to yosemite, lilypond and frescobaldi still works even though the MacPorts update is failing on cmake Error: org.macports.configure for port cmake returned: configure failure: command execution failed -- View this message in

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Xavier Noria
The cmake port needs Xcode 6.1 which still has not hit the App Store. Meanwhile it can be dowloaded from the Apple developer center if you have an account. ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Jacques Menu
FYI : Software update of Command line tools this morning on 10.9 upgraded Xcode to 6.1 (6A1052d). JM Le 21 oct. 2014 à 10:23:27, Xavier Noria f...@hashref.com a écrit : The cmake port needs Xcode 6.1 which still has not hit the App Store. Meanwhile it can be dowloaded from the Apple

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Gabriel Striewe
The cmake port needs Xcode 6.1 which still has not hit the App Store. Meanwhile it can be dowloaded from the Apple developer center if you have an account. I upgraded this morning to Yosemite. XCode 6.1 is now actually in the Store. I can't speak for Macports, but the homebrew

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Sven Axelsson
On 21 October 2014 16:55, Gabriel Striewe li...@gabriel-striewe.de wrote: I can't speak for Macports, but the homebrew lilypond actually fails installing. I will try tonight and possibly bring it up on the homebrew mailing list... Great. It is failing because of a Python-dev dependency. My own

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-21 Thread Paul Morris
Thanks for the info everyone. I've upgraded and LilyPond and Frescobaldi are working fine. Good to know I shouldn't try to do anything with MacPorts for now. Cheers, -Paul -- View this message in context:

Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-20 Thread Paul Morris
Anyone happen to know if there are any compatibility problems with LilyPond or Frescobaldi on the new Mac OSX 10.10 (Yosemite)? I have no reason to expect that there would be, but it would be nice to know before upgrading. Thanks in advance, -Paul -- View this message in context:

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-20 Thread Mike Solomon
On Oct 20, 2014, at 10:21 PM, Paul Morris p...@paulwmorris.com wrote: Anyone happen to know if there are any compatibility problems with LilyPond or Frescobaldi on the new Mac OSX 10.10 (Yosemite)? I have no reason to expect that there would be, but it would be nice to know before

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-20 Thread Philippe Massart
No problem with lilypond Frescobaldi runs without problem BUT be aware to not update your macports setup at this time. Some dependencies may cause some problems, as the have to be recompiled for the new system (with some possible problem with frescobaldi dependencies) Philippe Le 20 oct.

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-20 Thread Davide Liessi
2014-10-20 21:21 GMT+02:00 Paul Morris p...@paulwmorris.com: Anyone happen to know if there are any compatibility problems with LilyPond or Frescobaldi on the new Mac OSX 10.10 (Yosemite)? Speaking of Frescobaldi, if you installed it with MacPorts, I advise you to wait some time before

Re: Mac OSX 10.10 (Yosemite) and LilyPond compatibility?

2014-10-20 Thread MarcM
i have upgraded to yosemite, lilypond and frescobaldi still works even though the MacPorts update is failing on cmake Error: org.macports.configure for port cmake returned: configure failure: command execution failed -- View this message in context: