<div dir="ltr">That worked, thanks for the tip!<div><br></div><div>David</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 21, 2014 at 10:28 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sep 22, 2014, at 12:21 AM, <a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a> wrote:<br>
><br>
> Revision<br>
> 125581<br>
> Author<br>
> <a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a><br>
> Date<br>
> 2014-09-21 22:21:07 -0700 (Sun, 21 Sep 2014)<br>
> Log Message<br>
><br>
> abinit: temporarily include config.log in main log file for debugging buildbot configure failure on Mountain Lion.<br>
> Modified Paths<br>
><br>
> • trunk/dports/science/abinit/Portfile<br>
<br>
> +# This is a temporary measure for debugging configure failure on Mountain Lion buildslave.<br>
> +<br>
> +#checking for gcc... mpicc-mpich-mp<br>
> +#checking whether the C compiler works... no<br>
> +<br>
> +post-configure {<br>
> + system -W ${worksrcpath} "cat config.log"<br>
> +}<br>
<br>
Good idea! Unfortunately because the configure script fails, the post-configure block doesn't get run.<br>
<br>
You'd have to do something like set the configure.cmd to ./configure || true to continue on even when in fails.<br>
<br>
<br>
<br>
</blockquote></div><br></div>