[MacPorts] #50011: root6 - update to 6.06.00

[MacPorts]

#50011: root6 - update to 6.06.00
-----------------------+---------------------------------
  Reporter:  jonesc@…  |      Owner:  mojca@…
      Type:  update    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  haspatch maintainer
      Port:  root6     |
-----------------------+---------------------------------

Comment (by jonesc@…):

 Replying to [comment:12 jeremyhu@…]:
 > Replying to [comment:10 jonesc@…]:
 > > Replying to [comment:8 jeremyhu@…]:
 > > > You can probably blacklist < 504 and don't need to blacklist 3.4 and
 3.5.  I doubt you are compiling polly, which was the reason for the latest
 bump.
 > >
 > > Blacklist only < 504 is not enough, as then the system compilers on
 OSX 10.8 and 10.9 will be used, which do not work properly. Also don't i
 need to explicitly blacklist macports clang 3.4 to prevent it being used
 as the fallback. I've tested the settings as per my patch on all OSX
 versions 10.7 onwards and i think it covers all bases.
 >
 > There are no OS system compilers.  The compiler is shipped with Xcode.
 What makes you think that clang versions in `[504, 602)` do not work
 correctly for building llvm or clang?  I have no record of issues using
 Xcode 6.0 through 6.2 (which is what that change would allow) with stable
 versions of llvm.

 Sorry, I was imprecise with my language.

 My OSX10.8 VM has clang version

 {{{
 MacVM108 ~ > clang -v
 Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
 Target: x86_64-apple-darwin12.6.0
 Thread model: posix
 }}}

 from Xcode 5.1.1

 and for OSX 10.9
 {{{
 MacVM109 ~ > clang -v
 Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
 Target: x86_64-apple-darwin13.4.0
 Thread model: posix
 }}}

 from Xcode 6.2

 Both of these where unable to build this root6 update (Sorry, I cannot
 recall if the issue was specifically with the internal clang build, or
 root itself). It could also be due to the fact I wish to enable C++14
 support with this update.

 Forcing the use of MP's clang 3.7 fixed both cases.


 >
 > > > > I don't have time to investigate disabling tsan etc. right now...
 > > >
 > > > This makes no sense.  I highly doubt this has any impact on the
 root6 port.
 > >
 > > I thought the comment was referring to disabling tsan in the internal
 clang build built as part of the root6 port ?
 >
 > It would be built as part of compiler-rt, not clang, specifically.  And
 that only refers to very recent (within the past month) llvm trunk.
 Hopefully you're using more mature sources than that ;).

 I believe ROOT6 is using internal LLVM 3.7.0 sources (at least thats whats
 report when it configures the build, I don't know exactly what
 tag/revision etc. they are using).

 Chris

-- 
Ticket URL: <https://trac.macports.org/ticket/50011#comment:13>
MacPorts <https://www.macports.org/>
Ports system for OS X