Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
Cope with name clashes.
macOS 15's SDK pulls in headers related to when we include
. This causes our own regex_t implementation to clash with
the OS's regex_t implementation. Luckily our function names already had
pg_ prefixes, but the macros and typenames did not.
Include explicitly on all
