Bug 234696 - [Clang][Win] NotificationData.h(47,5): error: reference to 'UUID' is ambiguous
Summary: [Clang][Win] NotificationData.h(47,5): error: reference to 'UUID' is ambiguous
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2021-12-26 13:17 PST by Fujii Hironori
Modified: 2022-03-17 15:40 PDT (History)
2 users (show)

See Also:

repro (142 bytes, text/plain)
2021-12-26 17:03 PST, Fujii Hironori
no flags Details
workaround patch (1.24 KB, patch)
2022-03-17 15:40 PDT, Fujii Hironori
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Fujii Hironori 2021-12-26 13:17:10 PST
After r287412 (Bug 234571), Clang-cl can't compile WinCairo port.

FAILED: Source/WebCore/CMakeFiles/WebCore.dir/__/__/WebCore/DerivedSources/unified-sources/UnifiedSource-cbdfe323-28.cpp.obj 
C:\PROGRA~1\LLVM\bin\clang-cl.exe (..)UnifiedSource-cbdfe323-28.cpp
In file included from WebCore\DerivedSources\unified-sources\UnifiedSource-cbdfe323-28.cpp:6:
In file included from ..\..\Source\WebCore\Modules/notifications/NotificationData.cpp:27:
..\..\Source\WebCore\Modules\notifications/NotificationData.h(47,5): error: reference to 'UUID' is ambiguous
    UUID notificationID;
WTF\Headers\wtf/UUID.h(143,12): note: candidate found by name lookup is 'UUID'
using WTF::UUID;
C:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\shared\rpcdce.h(83,14): note: candidate found by name lookup is 'UUID'
typedef GUID UUID;
1 error generated.
Comment 1 Fujii Hironori 2021-12-26 17:03:23 PST
Created attachment 447994 [details]
Comment 2 Fujii Hironori 2021-12-26 17:07:39 PST
GCC and MSVC can compile, but Clang can't

Comment 3 Radar WebKit Bug Importer 2022-01-02 13:18:19 PST
Comment 4 Brady Eidson 2022-01-20 12:39:10 PST
We shouldn't have to make WebKit source code worse to handle one misbehaving compiler.

I'd wager we've had to deal with this type of thing in the past - Anybody have any ideas?
Comment 5 Fujii Hironori 2022-03-17 15:40:49 PDT
Created attachment 455038 [details]
workaround patch