On Mon, 2020-03-09 at 13:23 +0100, Martin Husemann wrote: > Stupid question: if that libc+++ is only designed to be C++11 and newer, > in what real world scenarios does it require exposing max_align_t? > > For sure you can easily compile the libc++.so* itself with proper standard > flags passed to the compiler, so it must be something else - or I'm missing > something. > max_align_t is exposed in public libc++ headers, so all applications built against libc++ (i.e. all C++ applications) need it visible. Given that Clang defaults to C++14 nowadays, I suppose it could be fixed by finding old -std= and replacing it. -- Best regards, Michał Górny
Attachment:
signature.asc
Description: This is a digitally signed message part