[MacPorts] #43917: ROOT6 : Update to first production release, 6.00.00

[MacPorts]

#43917: ROOT6 : Update to first production release, 6.00.00
-----------------------+---------------------------------
  Reporter:  jonesc@…  |      Owner:  mojca@…
      Type:  update    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  haspatch maintainer
      Port:  root6     |
-----------------------+---------------------------------

Comment (by mojca@…):

 Replying to [comment:32 jeremyhu@…]:
 > 1) You copy pasted everything from llvm-3.5, including the comment ;)

 Yes, I'm aware of that. But I don't yet feel comfortable messing with this
 yet: I'm not yet exactly sure how this `[info exists
 configure.cxx_stdlib]" works. I guessed your code must work on both 2.3
 and earlier, so I copied everything literally for now. It worked for me
 and I wrote "(copied from llvm-3.5)" in order not to forget to check how
 you would change the port ;)

 > 2) The checks for support of that variable aren't needed any more
 because it's supported in base 2.3.0 now, so you can remove the backwards
 compatible hacks.

 Does that mean that I should simply change

 {{{
 if {[info exists configure.cxx_stdlib]} {
     configure.cxx_stdlib libc++
 }
 }}}

 into

 {{{
 configure.cxx_stdlib libc++
 }}}

 I don't know what the proper change is which is why I didn't dare to do it
 (I see Chris' patch, but I need to figure out how this works exactly).

 > 3) What links against root, and what other libraries does root use?
 This will have a HUGE impact on that because anything that links against
 root6's libraries and any C++ libraries that root6 uses will need to use
 the libc++ runtime as well.

 At the moment I'm not aware of any port linking against root yet, even
 though some ports might start using it in future (iAida, Gate, ...).

 Root depends on the following ports:
 {{{
 expat, gmp, giflib, jpeg, libpng, lzma, pcre, tiff, zlib, xz, libgcc,
 graphviz, gsl, openssl, libxml2
 }}}
 even though with some tricks this list could be minimized to almost zero;
 I believe that root ships with most of these libraries, so one can simply
 use the built-in version; but then this would be done on < 10.9 only.

 > I've been using clang-3.5 fine on SnowLeopard and later for quite some
 time.  The issue is that you needed base 2.3 (trunk at the time), and you
 needed to chose libc++ as your C++ runtime in macports.conf (by setting
 "cxx_stdlib libc++").

 Thank you for explanation.

 > > interferes with the choice of the Fortran compiler
 >
 > Ugg.  See https://trac.macports.org/wiki/PortfileRecipes#fortran for
 setting up the fortran compiler.

 I think it's done that way already.

 Anyway, if I blacklist `*gcc*`, Fortran seems to compile just fine.

 > > compiler.fallback-append macports-clang-3.5 macports-clang-3.4
 >
 > Why append 3.5 before 3.4?  Also 3.4 is already in the fallback list
 (it's actually preferred over 3.3).

 I used it just in case (the higher version should have a better chance to
 work? ;), but I forgot that 3.5 is still a development version, so yes,
 3.4 should be listed before 3.5.

 The weird thing that I don't understand is that when I blacklist all gcc
 as well as system compiler on Lion, `macports-clang-3.3` was used (unless
 I blacklisted `macports-clang-3.3`), so I'm not sure if 3.4 is actually
 preferred over 3.3. But now that you mentioned it I'm curious to double
 check whether 3.3 or 3.4 would be selected by default.

 I actually need to check whether 3.3 works at all. The default compiler on
 Lion apparently doesn't.

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