You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Including <map> for C++ on macOS results in this error in the C++ headers:
...
/Applications/Xcode_14.2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk/usr/include/c++/v1/chrono:1583:12: error: reference to unresolved using declaration
static time_t to_time_t (const time_point& __t) _NOEXCEPT;
^
/Applications/Xcode_14.2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk/usr/include/c++/v1/ctime:79:1: note: using declaration annotated with 'using_if_exists' here
using ::time_t _LIBCPP_USING_IF_EXISTS;
This error started when the macOS runner was updated from 20230205.1 to 20230214.2. The build tools seem to be the same in both images, though, which makes this very surprising.
I cannot reproduce this locally with the current version of Xcode, which is why this seems to be a GitHub specific bug.
Hi @CendioOssman, seems I cannot reproduce the issue with using just simple repro code example (workflow output).
Could you provide some more clear repro steps?
Also, maybe your issue can be related to this PR - you could simply check if you manually install pkg-config (like brew install pkg-config) at the beginning of the pipeline.
Description
Including
<map>
for C++ on macOS results in this error in the C++ headers:This error started when the macOS runner was updated from 20230205.1 to 20230214.2. The build tools seem to be the same in both images, though, which makes this very surprising.
I cannot reproduce this locally with the current version of Xcode, which is why this seems to be a GitHub specific bug.
Platforms affected
Runner images affected
Image version and build link
20230214.2
https://github.com/TigerVNC/tigervnc/actions/runs/4211716928/jobs/7310247105
Is it regression?
Yes
Expected behavior
Code should compile fine, like it did with image 20230205.1:
Actual behavior
Crashes as described above.
Repro steps
Unclear. I have not tried to produce a minimal test case.
Looking at the crashing file, though, it seems like this should be sufficient to trigger the problem:
The text was updated successfully, but these errors were encountered: