[MacPorts] #43917: ROOT6 : Update to first production release, 6.00.00
MacPorts
noreply at macports.org
Fri Jun 6 21:00:45 PDT 2014
#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 jeremyhu@…):
Replying to [comment:62 jonesc@…]:
> Replying to [comment:61 mojca@…]:
> > I also don't quite understand the difference between these variants.
Why would one user want to explicitly specify `port install root6
+clang35`? Are there any real benefits of doing that? Would ROOT behave
differently in different situations?
>
> Don't forget the compiler used to build ROOT is then the same compiler
used interactively by ROOT when it is asked to compiler scripts etc. Thats
why the user might have a wish to pick a particular compiler.
Yes, but the variants set configure.compiler, so the variants select the
used compiler. We should try to avoid doing that as much as possible as
it's a nightmare to maintain. If you intend to select the compiler used
by root, that's fine, but don't set configure.compiler in that case.
> Yeah. I can find that myself ;) But how do you then manage to actually
view the log ? its so big it just hangs up my browser....
curl -LO https://build.macports.org/builders/buildports-snowleopard-
x86_64/builds/26843/steps/compile/logs/stdio/text
Then open it in a pager or text editor ... then go yell at WebKit to not
suck.
--
Ticket URL: <https://trac.macports.org/ticket/43917#comment:64>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list