> On Aug 11, 2016, at 11:14, Ryan Schmidt <ryandes...@macports.org> wrote: > >> On Aug 11, 2016, at 11:08, Jean-François Caron <jfca...@phas.ubc.ca> wrote: >> >> On Aug 11, 2016, at 09:55 , Lawrence Velázquez <lar...@macports.org> wrote: >> >>>> On Aug 11, 2016, at 9:05 AM, Jean-François Caron <jfca...@phas.ubc.ca> >>>> 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.
Actually, for some reason, packages don't exist for OS X 10.9 for any version of clang. I don't know why. I've triggered a build of clang-3.6 now and we'll see what it says. If that works we can trigger the other clang versions too. https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/876 _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
