diff options
| author | Mark Mentovai <mark@mentovai.com> | 2022-06-13 16:40:19 +0100 |
|---|---|---|
| committer | Jonathan Wakely <jwakely@redhat.com> | 2022-06-13 20:25:49 +0100 |
| commit | 254e88b3d7e8abcc236be3451609834371cf4d5d (patch) | |
| tree | a3c2a1bb7ebe557f2679d7071566a92aeeec5244 /gcc | |
| parent | 30cc1b65e4efa1a2c57fec5574fcae7a446b822f (diff) | |
| download | gcc-254e88b3d7e8abcc236be3451609834371cf4d5d.zip gcc-254e88b3d7e8abcc236be3451609834371cf4d5d.tar.gz gcc-254e88b3d7e8abcc236be3451609834371cf4d5d.tar.bz2 | |
libstdc++: Rename __null_terminated to avoid collision with Apple SDK
The macOS 13 SDK (and equivalent-version iOS and other Apple OS SDKs)
contain this definition in <sys/cdefs.h>:
863 #define __null_terminated
This collides with the use of __null_terminated in libstdc++'s
experimental fs_path.h.
As libstdc++'s use of this token is entirely internal to fs_path.h, the
simplest workaround, renaming it, is most appropriate. Here, it's
renamed to __nul_terminated, referencing the NUL ('\0') value that is
used to terminate the strings in the context in which this tag structure
is used.
libstdc++-v3/ChangeLog:
* include/experimental/bits/fs_path.h (__detail::__null_terminated):
Rename to __nul_terminated to avoid colliding with a macro in
Apple's SDK.
Signed-off-by: Mark Mentovai <mark@mentovai.com>
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions