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, 2014, at 21:22, Craig Treleaven <ctrelea...@macports.org> wrote: > At 2:39 PM -0700 10/14/14, nore...@macports.org wrote: >> The Buildbot has detected a failed build on builder >> buildports-mavericks-x86_64 while building MacPorts. >> Full details are available at: >> http://build.macports.org/builders/buildports-mavericks-x86_64/builds/7702 > > Can some kind person (Jeremy?) help me understand why the version of Clang on > the Mavericks buildbot is falling over while the Lion and MtnLion versions > don't even spit a warning? > > 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] > BOZO_end_boolean(b_multiple_frame_rate) > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ./test_dr.h:102:39: note: expanded from macro 'BOZO_end_boolean' > } while(!i_err && (s_decoded.name <= 12)); \ > ~~~~~~~~~~~~~~ ^ ~~ > (Complete log from the Mavericks buildbot attached.) > > If I understand correctly (always dicey given I'm not a C developer), this is > a unit test with (I guess) an awkward construct. The thing is, Clang on > MtnLion doesn't complain at all on the same code. > > What would be the best way to get past this? > > Thanks, > > Craig > <libdvbpsi_buildFail_Mavericks_2014Oct14.txt.zip>_______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
