Ryan Schmidt writes:
> On Sep 22, 2014, at 12:21 AM, dstru...@macports.org wrote:
>>
>> Revision
>> 125581
>> Author
>> dstru...@macports.org
>> Date
>> 2014-09-21 22:21:07 -0700 (Sun, 21 Sep 2014)
>> Log Message
>>
>> abinit: temporarily include config.log in main log file for debugging
>> buildbot configure failure on Mountain Lion.
>> Modified Paths
>>
>> • trunk/dports/science/abinit/Portfile
>
>> +# This is a temporary measure for debugging configure failure on Mountain
>> Lion buildslave.
>> +
>> +#checking for gcc... mpicc-mpich-mp
>> +#checking whether the C compiler works... no
>> +
>> +post-configure {
>> + system -W ${worksrcpath} "cat config.log"
>> +}
>
> Good idea! Unfortunately because the configure script fails, the
> post-configure block doesn't get run.
>
> You'd have to do something like set the configure.cmd to ./configure || true
> to continue on even when in fails.
Why don't we always include config.log in the output for a failure?
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
