|
| From: | Joseph Rushton Wakeling |
| Subject: | Re: compilation errors from Xcode's new standard library |
| Date: | Sun, 03 Nov 2013 14:00:58 +0100 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 |
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 how they could have cooked it to the point where what is AFAICS fairly standard C/C++ fails to compile with it.
Anyway, if you want to leave it here, no worries. I just thought it might be useful for other people if we could tie down what the source of the problem is.
Just for reference, do you have a log of what happens when you try running ./configure with CC=clang and CXX=clang++?
| [Prev in Thread] | Current Thread | [Next in Thread] |