Re: compilation errors from Xcode's new standard library

[Mike Solomon]

On Nov 3, 2013, at 1:15 PM, Joseph Rushton Wakeling <address@hidden> 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.
> 
> Well, what's odd is that your ./configure script says that it finds gcc:
> 
>> checking for gcc... gcc
>> checking whether the C compiler works... yes
>> checking for C compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... no
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
> 
> and g++:
> 
>> checking for g++... g++
>> checking whether we are using the GNU C++ compiler... yes
>> checking whether g++ accepts -g... yes
>> checking how to run the C++ preprocessor... g++ -E
>> checking for grep that handles long lines and -e... /usr/bin/grep
>> checking for egrep... /usr/bin/grep -E
>> checking whether we are using the GNU C++ compiler... (cached) yes
> 
> Yet your compile-time errors suggest that it is in fact clang that's being 
> used.
> 
> So, I suggest instead of just running ./configure, try instead:
> 
>    CC=clang CXX=clang++ ./configure
> 
> ... and then see if the build works.  (You can also add your custom CPPFLAGS 
> to that.)
> 

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.

Cheers,
MS