GCC-14 build fails on MacOSX using vcpkg

[garthgoodson]

I did this

Compiled curl using vcpkg on Mac OSX using gcc-14 (14.1) installed from brew.
macOS: 14.3-arm64
CLT: 15.3.0.0.1.1708646388

I got the following error:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/System/Library/Frameworks/Security.framework/Headers/SecBase.h:28,
from /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/System/Library/Frameworks/Security.framework/Headers/Security.h:27,
from /src//external/vcpkg/buildtrees/curl/src/curl-8_7_1-d8a6f70132.clean/lib/vtls/sectransp.c:57:
/Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFUserNotification.h:126:1: error:
attributes should be specified before the declarator in a function definition
126 | CF_INLINE CFOptionFlags CFUserNotificationCheckBoxChecked(CFIndex i) API_AVAILABLE(macos(10.0)) API_UNAVAILABLE(ios, watchos, tvos) {return ((
CFOptionFlags)(1UL << (8 + i)));}
| ^~~~~~~~~

I expected the following

vcpkg to compile the package

curl/libcurl version

curl-8_7_1-d8a6f70132

operating system

Darwin MacBook-Pro.local 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:59 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6030 arm64

[vszakats]

An Apple system header is failing to compile with gcc. It's been happening since macOS SDK 13, also with gcc 11 or 13.2.0. The solution is to use SDK 12, or Apple clang. Or Apple making their SDK headers gcc-compatible.

edit: Ref #10356 curl/curl-for-win@e2db3c4

[garthgoodson]

My system builds with gcc 13.2.

…

On Sat, May 18, 2024 at 11:07 PM Viktor Szakats ***@***.***> wrote: An Apple system header is failing to compile with gcc. It's been happening since macOS SDK 13, also with gcc 13.2. The solution is to use SDK 12, or Apple clang. Or Apple making their SDK headers gcc-compatible. — Reply to this email directly, view it on GitHub <#13700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANKTZEJYOL4ARPGYJVWI73ZDA6RFAVCNFSM6AAAAABH533JS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGEYTKNBRGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[vszakats]

The problem is detected in Apple headers, not in curl code. It may be a new incompatibility (and the old ones fixed?).

Can you try building without Secure Transport to see if that changes the result?