Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Rainer Müller
On 2016-01-26 20:01, Joshua Root wrote: > On 2016-1-27 05:52 , Rainer Müller wrote: >> On 2016-01-26 19:13, Joshua Root wrote: >>> On 2016-1-27 04:55 , Rainer Müller wrote: -stdlib=... is a linker flag not for ld itself, but for the clang++ to pass the correct library to ld. I t

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Joshua Root
On 2016-1-27 05:52 , Rainer Müller wrote: > On 2016-01-26 19:13, Joshua Root wrote: >> On 2016-1-27 04:55 , Rainer Müller wrote: >>> -stdlib=... is a linker flag not for ld itself, but for the clang++ to >>> pass the correct library to ld. >>> >>> I think this should be added to configure.ldflags i

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Rainer Müller
On 2016-01-26 19:13, Joshua Root wrote: > On 2016-1-27 04:55 , Rainer Müller wrote: >> -stdlib=... is a linker flag not for ld itself, but for the clang++ to >> pass the correct library to ld. >> >> I think this should be added to configure.ldflags in the same way it is >> handled for configure.cxx

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Joshua Root
On 2016-1-27 04:55 , Rainer Müller wrote: > -stdlib=... is a linker flag not for ld itself, but for the clang++ to > pass the correct library to ld. > > I think this should be added to configure.ldflags in the same way it is > handled for configure.cxxflags. Does that work (or even make sense) wh

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Rainer Müller
On 2016-01-26 17:27, Ryan Schmidt wrote: > I agree that MacPorts base only adds -stdlib=${configure.cxx_stdlib} > to configure.cxxflags, not configure.ldflags, but that's not > necessarily wrong, is it? Actually -stdlib=libc++ is also needed for linking to ensure the correct library will be linked

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread René J . V . Bertin
On Tuesday January 26 2016 08:27:12 Ryan Schmidt wrote: >If the build system just wants to link already-compiled objects, it doesn't >need compiler flags. If the build system wants to compile and link at the same >time, it's the build system's responsibility to add both the compiler flags >(CFL

Re: -stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread Ryan Schmidt
On Jan 26, 2016, at 4:35 AM, René J.V. Bertin wrote: > I just ran into a situation (building a Qt5 port) where for some reason > -stdlib=libc++ was added to configure.cxxflags but not to configure.ldflags . > That led to a failing final link. > > I worked around the issue by adding the option

-stdlib=libc++ added to configure.cxxflags but not configure.ldflags

2016-01-26 Thread René J . V . Bertin
Hi, I just ran into a situation (building a Qt5 port) where for some reason -stdlib=libc++ was added to configure.cxxflags but not to configure.ldflags . That led to a failing final link. I worked around the issue by adding the option myself if it is detected in cxxflags, but I wonder why this