cctools-886_3+llvm37 upgrade fails on Mac OS X 10.10.5 (Yosemite)

[ssrinath@…]

Hi,

I've scanned main.log file (attached) and tried various compiler options to no avail. Port cleaning, activating an older cctools package and trying to upgrade the rest etc., nothing seems to work. Any help would be highly appreciated.

[ssrinath@…]

main.log from cctools upgrade attempt

[ryandesign (Ryan Carsten Schmidt)]

Why is it "Using compiler 'MacPorts GCC 4.8'"?

[jeremyhu (Jeremy Huddleston Sequoia)]

Yeah, that's certainly not expected to work. Please don't set configure.compiler to macports-gcc-* and expect good results.

[ssrinath@…]

Replying to jeremyhu@…:

Yeah, that's certainly not expected to work. Please don't set configure.compiler to macports-gcc-* and expect good results.

Well, I've tried:

--configure.compiler=cc

--configure.compiler=clang

--configure.compiler=macports-clang

--configure.compiler=macports-clang-3.4

and in all cases the upgrade has failed with essentially the same main.log file. So, is there some magic flag with which I can signal macports that I *really* mean it when I don't want any variant of gcc to be the compiler?

[ssrinath@…]

main.log from using --configure.compiler=cc

[larryv (Lawrence Velázquez)]

Did you previously add “macports-gcc-4.8” to default_compilers in /opt/local/etc/macports/macports.conf?

[larryv (Lawrence Velázquez)]

As an aside, the syntax for specifying configure.compiler is

$ sudo port install whatever configure.compiler=clang

but that’s not really relevant because the build should not be defaulting to macports-gcc-4.8.

[jeremyhu (Jeremy Huddleston Sequoia)]

Yeah, what happens when you don't try to override the compiler? Using macports-gcc-* as a default compiler is not supported and will likely fail a lot of the time.