ROOT update to 5.34.10 + various compiler improvements

[cjones051073 (Chris Jones)]

Hi,

The attached update bumps the ROOT port to 5.34.10.

It also reworks the gcc variants to address issues with mixing c++ runtimes, by no longer using these variants to set the c/c++ compilers. They are now only used to set the fortran compiler.

The cocoa variant is now update to use compiler black and fall back lists to make sure a compatible clang compiler is always used. (Can only test on OSX 10.8 with Xcode 4.6.3 so rely on reports from others for problems with other combinations).

cheers Chris

[mf2k (Frank Schima)]

r110912. Thanks! I also fixed some minor lint spacing warnings.

[gnw3]

config.log for Snow Leoaprd build using default options

[gnw3]

main.log for failed Snow Leopard build using default options

[gnw3]

root 5.34.10 builds on Snow Leopard (Xcode 3.2.6) using the default options and with macports' FTGL deactivated. Using +clang33 builds even with active FTGL. I have attached logs from a failed build. I would have guessed that the library search is finding macports FTGL rather than ROOT's internal FTGL, but it is a bit of a surprise that +clang33 would affect library search.

[cjones051073 (Chris Jones)]

I've seen things like this in the past, but they went away, probably when I updated to 10.7 or a newer Xcode.. I only have 10.8 + Xcode 4.6.3 to test with, and there I don't see the problem.

I agree with your idea that it could be the ROOT configuration picking up the library when it shouldn't be (as it should be forced into building its own). As I cannot debug this myself there is nothing much I can do (other perhaps put a check in that causes the port build to error out on OSX 10.6 if ftgl is instead, instructing the user to deactivate it for the duration of the ROOT build). If someone else wishes to poke around to see if they can figure out whats wrong, be my guest ;)

Chris

[gnw3]

Replying to jonesc@…:

I've seen things like this in the past, but they went away, probably when I updated to 10.7 or a newer Xcode.. I only have 10.8 + Xcode 4.6.3 to test with, and there I don't see the problem.

I agree with your idea that it could be the ROOT configuration picking up the library when it shouldn't be (as it should be forced into building its own). As I cannot debug this myself there is nothing much I can do (other perhaps put a check in that causes the port build to error out on OSX 10.6 if ftgl is instead, instructing the user to deactivate it for the duration of the ROOT build). If someone else wishes to poke around to see if they can figure out whats wrong, be my guest ;)

Just to clarify -- configure is given the "--enable-builtin-ftgl" option, so config.log has:

Checking whether to build included libftgl
Result: yes

I verified that ROOT's FTGL library gets built, but from the link errors it seems that macport's version is used to link unless the +clang33 variant is requested.