Re: fixing devel/gmp for MacOS X/clang

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Fri, Sep 20, 2013 at 01:58:03PM +0200, Jens Rehsack wrote:
> 
> Am 20.09.2013 um 13:52 schrieb Adam Ciarciński <adam%NetBSD.org@localhost>:
> 
> >> Well - no :)
> >> 
> >> $ ls -l 
> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include/c++/4.2.1/
> >> total 168
> >> […]
> >> -rw-r--r--   1 root  wheel   2214 19 Sep 13:58 string
> >> drwxr-xr-x  57 root  wheel   1938 20 Jun  2012 tr1
> >> -rw-r--r--   1 root  wheel   5929 19 Sep 13:58 typeinfo
> >> -rw-r--r--   1 root  wheel   2789 19 Sep 13:58 utility
> >> […]
> >> 
> >> $ $ find 
> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include
> >>  -name tuple
> >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/include/c++/4.2.1/tr1/tuple
> > 
> > Well, yes. These includes are for libc++, not libstdc++. Provide 
> > -stdlib=libc++ and it should compile just fine.
> 
> 
> Okay - the symbolic link isn't needed, just the -stdlib=libc++ flag


> Does that patch looks better for you?

Please hold off on this. I strongly believe that it should become the
default after the branch and be handled in a unified fashion.

Joerg