Re: Clang: Mavericks v. the rest (was Re: buildbot failure in MacPorts on buildports-mavericks-x86_64)

2014-10-15 Thread Chris Jones
Hi, The warning is correct. If s_decoded.name is a boolean then s_decoded.name = 12 is always true. OSX10.9 has a newer clang, which issues a warning in this case (-Wtautological-constant-out-of-range-compare), older OSes have older clang versions that do not. Finally -Werror turns it into

Re: Clang: Mavericks v. the rest (was Re: buildbot failure in MacPorts on buildports-mavericks-x86_64)

2014-10-15 Thread Craig Treleaven
Thanks, all. A conditional patch (... ${os.major} = 13 ...) and at least it builds. I will follow up upstream. Craig At 8:43 AM +0100 10/15/14, Chris Jones wrote: The warning is correct. If s_decoded.name is a boolean then s_decoded.name = 12 is always true. OSX10.9 has a newer clang,

Re: Clang: Mavericks v. the rest (was Re: buildbot failure in MacPorts on buildports-mavericks-x86_64)

2014-10-14 Thread Jeremy Lavergne
I’d assume (even though I’m not that Jeremy) that the clang on mavericks is newer and simply has more warnings as errors. The warning flags in the brackets are what were triggered: do they exist on the older compiler version and if so are they active? That’s probably all it is. On Oct 14,

Re: Clang: Mavericks v. the rest (was Re: buildbot failure in MacPorts on buildports-mavericks-x86_64)

2014-10-14 Thread Lawrence Velázquez
On Oct 14, 2014, at 9:22 PM, Craig Treleaven ctrelea...@macports.org wrote: Mavericks Clang errors out with the following: test_dr.c:49:3: error: comparison of constant 12 with expression of type 'bool' is always true [-Werror,-Wtautological-constant-out-of-range-compare]