[patch] libstdc++/61011 fix --disable-libstdcxx in top-level configure

[Jeff Law]

On 05/30/14 11:09, Jonathan Wakely wrote:
> PING
>
> This is a change to top-level configure, not libstdc++ itself, so I
> need approval.
>
>
> On 20/05/14 15:59 +0100, Jonathan Wakely wrote:
>> On 20/05/14 15:53 +0100, Jonathan Wakely wrote:
>>> The first part of this patch fixes the PR, we should be adding
>>> target-libstdc++-v3 to noconfigdirs, not libstdc++-v3.
>>>
>>> The second part disables the target libs that can't be bootstrapped
>>> without libstdc++.
>>>
>>> libcilkrts and libsanitizer use lots of std:: stuff.
>>> libitm only uses std::atomic, but in any case fails to build when
>>> --disable-libstdcxx is used, with this error:
>>>
>>> xg++: error: unrecognized command line option
>>> ‘-funconfigured-libstdc++-v3’
>>>
>>> Bootstrapped with and without --disable-libstdcxx and tested on
>>> x86_64-linux.
>>>
>>>      PR libstdc++/61011
>>>      * configure.ac (--disable-libstdcxx): Set noconfigdirs correctly.
>>>      Disable libcilkrts, libitm, libsanitizer when not building
>>> libstdc++.
>>>      * configure: Regenerate.
>>>
>>> OK for trunk?
>>
>> With the patch this time ...
>
> commit c384fef85bca43046b65eb02267169a5613af2b8
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date:   Tue May 20 12:13:43 2014 +0100
>
>         PR libstdc++/61011
>         * configure.ac (--disable-libstdcxx): Set noconfigdirs correctly.
>         Disable libcilkrts, libitm, libsanitizer when not building
> libstdc++.
>         * configure: Regenerate.
While it may be a top-level configure change, I'd consider it part of 
the libstdc++ world by extension.  Approved.

Jeff