First time contributor, adding p1004 for C++20 -- constexpr std::vector

Jonathan Wakely jwakely@redhat.com
Thu Jul 30 20:16:04 GMT 2020


On 30/07/20 16:11 -0400, Josh Marshall via Libstdc++ wrote:
>How do you mean broken by design?

Something about it means that GCC can't detect a working C library,
and so it can't build a fully functional libstdc++. It also seems to
require messing about with include paths to make the compiler work,
because of the funky paths required for the transactions+rollback
feature, I assume.

Unless you want to debug why it doesn't support libstdc++ properly, I
wouldn't recommend it as platform for libstdc++ development.


>On Thu, Jul 30, 2020 at 3:57 PM Jonathan Wakely <jwakely@redhat.com> wrote:
>>
>> On 30/07/20 13:37 -0400, Josh Marshall via Libstdc++ wrote:
>> >Which branch should I be branching off of to develop from?  Master
>> >looks like it is having compile failures:
>>
>> The master branch is the right one.
>>
>> It looks like you're using guix, which seems to be broken by design as
>> far as I can tell.
>>
>> The strtof function is not detected during configure:
>> https://lists.gnu.org/archive/html/guix-devel/2020-06/msg00131.html
>>
>> You might want to consider using an OS that can configure libstdc++
>> properly if you plan to work on libstdc++.
>>
>> I've committed the attached patch to master, which should fix those
>> errors.
>>
>> Tested x86_64-linux, committed to master.
>>
>



More information about the Libstdc++ mailing list