<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Dec 17, 2013 at 4:49 PM, Ryan Schmidt <span dir="ltr"><<a href="mailto:ryandesign@macports.org" target="_blank">ryandesign@macports.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5"><br>
On Dec 17, 2013, at 08:28, Eric A. Borisch wrote:<br>
<br>
> This ticket <a href="https://trac.macports.org/ticket/41836" target="_blank">https://trac.macports.org/ticket/41836</a> describes an issue where (apparently, I don't have a matching system to test) 10.8.5 and XCode 5.0.2 are installed.<br>
><br>
> The user installed (I'm guessing from buildbot archive) mpich-default, which wraps /usr/bin/llvm-gcc-4.2. In the setup mentioned, this doesn't exist. (Which is why I'm saying it came from the archive rather than a local build -- mpich wraps the compiler it was built with.)<br>
><br>
> Any thoughts on how to fix this? What version of Xcode (esp. clang) is on the 10.8 buildbot?<br>
> llvm-gcc-4.2 gets used if clang is blacklisted:<br>
><br>
> < from the Portfile><br>
> # Linker for Apple clang version 421.11.66 segfaults<br>
> # See <a href="https://trac.macports.org/ticket/36654#comment:9" target="_blank">https://trac.macports.org/ticket/36654#comment:9</a><br>
> compiler.blacklist-append {clang >= 421.11.66 < 425.0.24}<br>
> </Portfile><br>
<br>
</div></div>Evidently the 10.8 buildbot has a version of Xcode that has a version of clang in that build number range.<br>
<br>
I guess the user should rebuild mpich-default from source (the “-s”) flag, or not use mpich-default. Ports that hardcode compilers discovered at build time are considered a bug, so you’re on your own since that bug appears to be your intention with this port.<br>
</blockquote></div><br></div><div class="gmail_extra">Well, MPICH provides compiler wrappers (in addition to libraries.) Kinda hard to be a compiler wrapper without naming the compiler. :)<br></div><div class="gmail_extra">
<div class="gmail_extra"><br></div><div class="gmail_extra">I had the user rebuild from source already, and that proved to fix the issue -- we have nailed down what is happening.</div><div><br></div></div><div class="gmail_extra">
Perhaps it would be best if I mark the port as not binary distributable. Or I could as a post-activate check that would alert the user if the embedded compiler doesn't exist on the system. Decisions, decisions.</div><div class="gmail_extra">
<br></div><div class="gmail_extra"> - Eric</div></div>