Closed
Bug 1225642
Opened 9 years ago
Closed 9 years ago
Add -Wno-parentheses-equality back to Clang builds that need it
Categories
(NSS :: Build, defect)
Tracking
(firefox45 affected)
RESOLVED
FIXED
3.22
Tracking | Status | |
---|---|---|
firefox45 | --- | affected |
People
(Reporter: jld, Assigned: jld)
Details
Attachments
(1 file)
1.33 KB,
patch
|
mt
:
review+
mt
:
checked-in+
|
Details | Diff | Splinter Review |
Bug 1211568 seems to have slightly broken the OS X build (at least with the compiler version that calls itself "Apple LLVM version 7.0.0 (clang-700.1.76)") while refactoring the -Werror handling, by adding -Wno-parentheses-equality to the wrong make variable.
Assignee | ||
Comment 1•9 years ago
|
||
On further thought, this probably affects Clang on other platforms.
Summary: Add -Wno-parentheses-equality back to OS X build → Add -Wno-parentheses-equality back to Clang builds that need it
Assignee | ||
Comment 2•9 years ago
|
||
Attachment #8688670 -
Flags: review?(martin.thomson)
Comment 3•9 years ago
|
||
Comment on attachment 8688670 [details] [diff] [review] One-line patch Review of attachment 8688670 [details] [diff] [review]: ----------------------------------------------------------------- https://hg.mozilla.org/projects/nss/rev/6a631abbf25d
Attachment #8688670 -
Flags: review?(martin.thomson)
Attachment #8688670 -
Flags: review+
Attachment #8688670 -
Flags: checked-in+
Comment 4•9 years ago
|
||
Jed, do you think that this fix needs to be uplifted to NSS 3.21? (Keeping in mind that I don't know how we might do that and that we might want to release 3.22 soon-ish anyway.)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.22
Assignee | ||
Comment 5•9 years ago
|
||
(In reply to Martin Thomson [:mt:] from comment #4) > Jed, do you think that this fix needs to be uplifted to NSS 3.21? (Keeping > in mind that I don't know how we might do that and that we might want to > release 3.22 soon-ish anyway.) …maybe. NSS_3_21_RTM fails to build for me on OS X 10.10, which is bad, but the other part of this (which I just noticed) is that I'm using ccache. There isn't an expression of the form ((e1 == e2)) in the original source, but there are some after preprocessing expands macros; clang has enough information to suppress the warning in that case if it's compiling normally, but ccache runs preprocessing separately. So this wouldn't affect people not using ccache. But it should be low risk for uplifting if 3.21.1 is going to happen.
Version: trunk → 3.21
Comment 6•9 years ago
|
||
Yes, I discovered that ccache has some unfortunate interactions with clang. I have turned it off as a result. It took be a while to discover that Fedora rewrites your path when ccache is installed so that it intercepts calls to clang/gcc/cc. I'll try to remember this if we need a 3.21.1. My hope is to release 3.22 pretty soon in any case.
You need to log in
before you can comment on or make changes to this bug.
Description
•