Closed Bug 1217612 Opened 9 years ago Closed 7 years ago

clang isn't always detected properly

Categories

(NSS :: Libraries, defect, P3)

3.21
All
Linux
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mt, Unassigned)

Details

The build currently identifies the compiler by calling `$(CC) -?` and splitting on colon.  This has worked, but the recent version of clang I have on my machine reports itself as "clang-3.8".  Since we look for clang before enabling -Werror, this has the effect of disabling warnings-as-errors for this compiler.
Is this still relevant with/for GYP?
Priority: -- → P3
Flags: needinfo?(martin.thomson)
Well, it's probably still relevant, but I don't care any more.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(martin.thomson)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.