Re: compilation errors from Xcode's new standard library

2013-11-14 Thread Jack Howarth
On Thu, Nov 14, 2013 at 02:19:32PM -0500, Jack Howarth wrote: >Just to clarify, the failures here are due to Mac OS X 10.9 replacing > libstdc++ > with the new llvm libc++ c++ library. You won't be able to reproduce these > failures > on other platforms that still use the libstdc++ c++ librar

Re: compilation errors from Xcode's new standard library

2013-11-14 Thread Jack Howarth
Just to clarify, the failures here are due to Mac OS X 10.9 replacing libstdc++ with the new llvm libc++ c++ library. You won't be able to reproduce these failures on other platforms that still use the libstdc++ c++ library. FYI, the next platform to adopt libc++ is slated to be FreeBSD.

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 2:20 PM, David Kastrup wrote: > Mike Solomon writes: > >> On Nov 3, 2013, at 1:50 PM, David Kastrup wrote: >> >>> Shrug. At any rate, it would be important to get some feedback >>> regarding installation of the stock LilyPond binary distribution on the >>> newest OSX. It

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread David Kastrup
Mike Solomon writes: > On Nov 3, 2013, at 1:50 PM, David Kastrup wrote: > >> Shrug. At any rate, it would be important to get some feedback >> regarding installation of the stock LilyPond binary distribution on the >> newest OSX. It would be good if that worked before we put out 2.18. > > http

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 2:03 PM, Mike Solomon wrote: > > On Nov 3, 2013, at 2:00 PM, Joseph Rushton Wakeling > wrote: > >> On 03/11/13 13:36, Mike Solomon wrote: >>> Doesn’t work, but all the files in flower compile fine with gcc, so I’m a >>> happy camper. >>> Apple’s home cooked clang is not fr

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 2:00 PM, Joseph Rushton Wakeling wrote: > On 03/11/13 13:36, Mike Solomon wrote: >> Doesn’t work, but all the files in flower compile fine with gcc, so I’m a >> happy camper. >> Apple’s home cooked clang is not free software, so there’s no reason to >> expect free software

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 13:36, Mike Solomon wrote: Doesn’t work, but all the files in flower compile fine with gcc, so I’m a happy camper. Apple’s home cooked clang is not free software, so there’s no reason to expect free software to compile with it. I don’t mind giving up on it. It's difficult to see

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 1:50 PM, David Kastrup wrote: > Mike Solomon writes: > >> Apple’s home cooked clang is not free software, so there’s no reason >> to expect free software to compile with it. > > Non sequitur. There is nothing wrong with trying to bring some more > taste of free software to

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread David Kastrup
Mike Solomon writes: > Apple’s home cooked clang is not free software, so there’s no reason > to expect free software to compile with it. Non sequitur. There is nothing wrong with trying to bring some more taste of free software to people in the Apple jails. Now there are alternative means, so

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 1:15 PM, Joseph Rushton Wakeling wrote: > On 03/11/13 12:33, Mike Solomon wrote: >> >> [ ... snip ... ] >> >> …these fonts are always a pain, but I usually figure out some way to cheat >> and get them in there. But that shouldn’t have anything to do with the >> compiler.

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 12:33, Mike Solomon wrote: [ ... snip ... ] …these fonts are always a pain, but I usually figure out some way to cheat and get them in there. But that shouldn’t have anything to do with the compiler. Well, what's odd is that your ./configure script says that it finds gcc: chec

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 11:45 AM, Joseph Rushton Wakeling wrote: > On 03/11/13 11:18, Mike Solomon wrote: >> Yeah, the output is fine (clean bill of health, all systems go). I had to >> specifically set CPPFLAGS to deal w/ some homebrew issues, but otherwise >> nothing out of the ordinary. > > Ah

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 11:18, Mike Solomon wrote: Yeah, the output is fine (clean bill of health, all systems go). I had to specifically set CPPFLAGS to deal w/ some homebrew issues, but otherwise nothing out of the ordinary. Ahh, OK. That's odd; OK, I accept that the clang you have has been a little

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 11:15 AM, Joseph Rushton Wakeling wrote: > On 03/11/13 11:00, Mike Solomon wrote: >> That’s fine, I’ll download gcc. > > From what I understand from friends who've experienced the same, you'll have > to manually remove/rewrite some of the symlinks. > > Just to check -- bef

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 11:00, Mike Solomon wrote: That’s fine, I’ll download gcc. From what I understand from friends who've experienced the same, you'll have to manually remove/rewrite some of the symlinks. Just to check -- before you rework everything -- did you manually re-run the configure script

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 10:37 AM, David Kastrup wrote: > Joseph Rushton Wakeling writes: > >> On 03/11/13 10:09, Mike Solomon wrote: >>> Looks like some files in flower don't play nice with the most recent >>> version of the standard library bundled with Xcode… >>> >>> Any ideas for how to proceed?

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
On Nov 3, 2013, at 10:50 AM, Joseph Rushton Wakeling wrote: > On 03/11/13 10:37, David Kastrup wrote: >> We committed a few Clang-related fixes in the past, I think mostly due >> to Graham's insistence/testing, but I think at some point of time the >> "compile with Clang" ambition just faded. >

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 10:37, David Kastrup wrote: We committed a few Clang-related fixes in the past, I think mostly due to Graham's insistence/testing, but I think at some point of time the "compile with Clang" ambition just faded. I just tried a clang-based build on my Ubuntu 13.10 system, just to see

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread David Kastrup
Joseph Rushton Wakeling writes: > On 03/11/13 10:09, Mike Solomon wrote: >> Looks like some files in flower don't play nice with the most recent >> version of the standard library bundled with Xcode… >> >> Any ideas for how to proceed? > > If I understand right (I'm not a Mac user), latest Xcode

Re: compilation errors from Xcode's new standard library

2013-11-03 Thread Joseph Rushton Wakeling
On 03/11/13 10:09, Mike Solomon wrote: Looks like some files in flower don't play nice with the most recent version of the standard library bundled with Xcode… Any ideas for how to proceed? If I understand right (I'm not a Mac user), latest Xcode has clang as default compiler, and symlinks t

compilation errors from Xcode's new standard library

2013-11-03 Thread Mike Solomon
Looks like some files in flower don't play nice with the most recent version of the standard library bundled with Xcode… clang: warning: argument unused during compilation: '-mno-fused-madd' clang: warning: argument unused during compilation: '-L/usr/local/lib' In file included from /Users/mikes