[petsc-dev] Why does configure ignore compiler output?
Matthew Knepley
knepley at gmail.com
Mon Mar 18 20:10:41 CDT 2013
On Mon, Mar 18, 2013 at 9:03 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Ever since at least here, configure has ignored compiler output by default.
>
>
> https://bitbucket.org/petsc/petsc/commits/08bdf6bce1142b6c3d4d318bdb8e3320d9f5808d#Lconfig/framework.pyT287
>
> This means that all the checks in filterCompileOutput don't even run.
> What's the rationale for this?
>
It was before that commit, as you can see that I just use the 1 that was
already there.
I think it was that compilers too often spewed a bunch of meaningless crap.
Matt
>
> Possible ERROR while running compiler: error message =
> {"/tmp/petsc-NZgbtU/PETSc.Configure/conftest.c", line 3: warning:
> attribute "unused" is unknown, ignored
> "/tmp/petsc-NZgbtU/PETSc.Configure/conftest.c", line 3: warning:
> attribute "unused" is unknown, ignored
> "/tmp/petsc-NZgbtU/PETSc.Configure/conftest.c", line 9: warning:
> attribute "unused" is unknown, ignored
> }
> Source:
> #include "confdefs.h"
> #include "conffix.h"
> __attribute((unused)) static int myfunc(__attribute((unused)) void *name){
> return 1;}
>
> int main() {
> int i = 0;
> int j = myfunc(&i);
> typedef void* atype;
> __attribute((unused)) atype a;
> ;
> return 0;
> }
> Pushing language C
> Popping language C
> sh: /home/jed/usr/mpich-sun/bin/mpicc -o
> /tmp/petsc-NZgbtU/PETSc.Configure/conftest -PIC
> /tmp/petsc-NZgbtU/PETSc.Configure/conftest.o -ldl
> Executing: /home/jed/usr/mpich-sun/bin/mpicc -o
> /tmp/petsc-NZgbtU/PETSc.Configure/conftest -PIC
> /tmp/petsc-NZgbtU/PETSc.Configure/conftest.o -ldl
> sh:
> Defined "UNUSED" to "__attribute((unused))"
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130318/42c76704/attachment.html>
More information about the petsc-dev
mailing list