Re: [125581] trunk/dports/science/abinit/Portfile
Ryan Schmidt writes:
>> On Sep 22, 2014, at 1:27 AM, Sean Farley wrote:
>>
>>
>> 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?
>
> IIRC, last time this came up we decided the config.log is enormous and might
> make it harder to see the error printed by the configure script, which is
> sometimes easier to understand than the extensive information in the
> config.log. Therefore we settled on just printing the location of the
> config.log.
This is a conundrum now since we can't (easily) access the config.log on
the buildbots. We could probably just zip the log file and print from
that since it'd be fairly easy. It'd also save a step for the end user:
they'd get a location to a single zipped logfile to upload to a ticket.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [125581] trunk/dports/science/abinit/Portfile
> On Sep 22, 2014, at 1:27 AM, Sean Farley wrote:
>
>
> 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?
IIRC, last time this came up we decided the config.log is enormous and might
make it harder to see the error printed by the configure script, which is
sometimes easier to understand than the extensive information in the
config.log. Therefore we settled on just printing the location of the
config.log.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [125581] trunk/dports/science/abinit/Portfile
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
Re: [125581] trunk/dports/science/abinit/Portfile
> On Sep 22, 2014, at 12:50 AM, David Strubbe wrote: > > That worked, thanks for the tip! Yup, that answers the questions: configure:10604: checking for C compiler version configure:10613: mpicc-mpich-mp --version >&5 /opt/local/bin/mpicc-mpich-mp: line 265: /opt/local/bin/clang-mp-3.4: No such file or directory configure:10624: $? = 127 configure:10613: mpicc-mpich-mp -v >&5 mpicc for MPICH version 3.1.2 /opt/local/bin/mpicc-mpich-mp: line 269: /opt/local/bin/clang-mp-3.4: No such file or directory configure:10624: $? = 127 configure:10613: mpicc-mpich-mp -V >&5 /opt/local/bin/mpicc-mpich-mp: line 265: /opt/local/bin/clang-mp-3.4: No such file or directory configure:10624: $? = 127 configure:10613: mpicc-mpich-mp -qversion >&5 /opt/local/bin/mpicc-mpich-mp: line 265: /opt/local/bin/clang-mp-3.4: No such file or directory configure:10624: $? = 127 configure:10644: checking whether the C compiler works configure:10666: mpicc-mpich-mp -pipe -O3 -arch x86_64 -I/opt/local/include -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 conftest.c >&5 /opt/local/bin/mpicc-mpich-mp: line 265: /opt/local/bin/clang-mp-3.4: No such file or directory configure:10670: $? = 127 configure:10708: result: no ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [125581] trunk/dports/science/abinit/Portfile
That worked, thanks for the tip!
David
On Sun, Sep 21, 2014 at 10:28 PM, Ryan Schmidt
wrote:
> 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.
>
>
>
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [125581] trunk/dports/science/abinit/Portfile
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.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
