On Aug 11, 2016, at 11:08, Jean-François Caron <[email protected]> wrote: > > On Aug 11, 2016, at 09:55 , Lawrence Velázquez <[email protected]> wrote: > >>> On Aug 11, 2016, at 9:05 AM, Jean-François Caron <[email protected]> >>> wrote: >>> >>> I’m glad my idea wasn’t as silly as I had thought. Maybe this will go >>> somewhere. >>> >>> I needed to build clang locally because I use the +analyzer variant. Maybe >>> this variant could be made default, since it has no performance impacts and >>> shouldn’t cause any problems for users who ignore the analyzer. There are >>> probably more people who currently do +analyzer than people who would >>> insist on -analyzer if it were default. >> >> The +analyzer variant is already enabled by default. Which clang port are >> you building, and on what OS? >> >> vq > > This was for a regular “port upgrade outdated” of clang-3.6 @3.6.2_3+analyzer > to clang-3.6 @3.6.2_4+analyzer. > > I am on OSX 10.9.5. Maybe it’s too old.
We build packages for 10.6 and later. But they take time to compile and upload. You may have been upgrading between the time that the update was committed and the time that the build completed. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
