[Webkit-unassigned] [Bug 108089] New: "clang: warning: not using the clang compiler for C++ inputs" due to hard-coding of /usr/bin/clang in WebCore.gyp
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jan 28 09:35:24 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=108089
Summary: "clang: warning: not using the clang compiler for C++
inputs" due to hard-coding of /usr/bin/clang in
WebCore.gyp
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
OS/Version: Mac OS X 10.6
Status: NEW
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: mike at w3.org
http://trac.webkit.org/changeset/140925 for bug 107984 changed Source/WebCore/WebCore.gyp/WebCore.gyp so that it now hardcodes "/usr/bin/clang" as an argument for --preprocessor switch that's fed to the part of the build that preprocesses the bindings idl files.
In my OSX 10.6.8 environment, that change causes the build to generate hundreds of "clang: warning: not using the clang compiler for C++ inputs" messages.
Why not just have "clang" there instead of "/usr/bin/clang"? That way you could just have this part of the build using the clang that the rest of the build uses; e.g., if I have my environment set up for building Chromium with clang in $CHROME/src/third_party/llvm-build/Release+Asserts/bin the idl preprocessing would use that clang too.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list