mpich-default @3.0.4_8

[kobayos]

/usr/bin/llvm-gcc-4.2 is adopted as a default c compiler for mpicc-mp in this port with default variants "+gcc48" even if the compiler does not exist. This may happens if Xcode 5 is cleanly installed since Xcode 5 does not include the compiler.

As a consequence, although installation of this port successfully finished, an error, "/opt/local/bin/mpicc-mp: line 290: /usr/bin/llvm-gcc-4.2: No such file or directory", always occurs if mpicc-mp is used. I experienced this error on a combination of OS X 10.8.5, Xcode 5.0.2. Xcode 5 was cleanly installed, not upgraded from Xcode 4.

This error does not occur if Xcode 5 is upgraded from Xcode 4. In this case, it seems that /usr/bin/llvm-gcc-4.2 is still existing and usable. I checked it on another computer. Its combination of the versions of OS X and Xcode is the same with the system in which the error occurs. In this system, Xcode 5 was upgraded from Xcode 4.

Additionally, if a variant "+gcc47", the c compiler is changed to /usr/bin/clang.

Thank you.

[eborisch (Eric A. Borisch)]

Compiled from source, or installed from archive? Try installing from source.

The compiler that mpicc-mp wraps is the compiler it was built with, so I'm guessing this was installed via archive from the buildbot. Perhaps we need to add some additional checks to when an archive fetch (vs. local build) is permitted.

[kobayos]

It was installed from the archive.

I installed it by compiling from the source few minutes ago, and confirmed that the default compiler was successfully changed to /usr/bin/clang.

Thank you very much for your advice.

[eborisch (Eric A. Borisch)]

Thanks for the update. Switching to a non-default variant (your initial +gcc47 test) also forced a local build, so everything seems consistent.

I will poke at how to avoid this situation on the dev mailing list.