[petsc-dev] Compiling C code with C compiler

Satish Balay balay at mcs.anl.gov
Mon Apr 4 21:00:07 CDT 2011


ok '-x c++' is getting rid of the warning.

asterix:/home/balay/junk>clang sizeof.c
asterix:/home/balay/junk>clang++ sizeof.c
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
asterix:/home/balay/junk>clang++ -x c++ sizeof.c
asterix:/home/balay/junk>


satish


On Mon, 4 Apr 2011, Satish Balay wrote:

> There is clang and clang++ - but still they insist on throwing this warning.
> 
> When I invoke clang++ - I want c++. So I'm not sure whats so ambiguous
> that they should throw this warning.
> 
> And what does this depricate mean? That  'clang++ foo.c' will create C code?
> 
> Then why have both clang and clang++?
> 
> satish
> 
> On Mon, 4 Apr 2011, Barry Smith wrote:
> 
> > 
> >    configure.log ????
> > 
> >    What about passing the compiler option -x C++? Or maybe you are already doing that but I would't know because you didn't send configure.log 
> > 
> >     It's bad enough when our ignorant users don't send necessary configure.log files but you?
> > 
> >    Barry
> > 
> > On Apr 4, 2011, at 8:33 PM, Sean Farley wrote:
> > 
> > > When specifying --with-clanguage=C++ (as required by sieve) all C code (any .c file) is still compiled with the C++ compiler. This behavior is deprecated as clang will warn you:
> > > 
> > > clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated
> > > 
> > > C is not a subset of C++ and treats structs very differently than C++. This should really be handled correctly but I can't read the conf/rules file no more than I can read Greek.
> > > 
> > > Sean
> > > <make.log>
> > 
> > 
> 
> 




More information about the petsc-dev mailing list