you should select carefully what type of warnings to disable in this way.
in my example i turned off warnings only for unused variables and
parameters that in general should not pose any serious threat to your
code (in fact i cannot imagine an example in which such approach would
fail, do you have
On Wed, 1 Jun 2011, Derek Gaston wrote:
> Very cool do we need something like a
> LIBMESH_INCLUDE_NO_WARN_BEGIN and LIBMESH_INCLUDE_NO_WARN_END that
> could be set to compiler specific #pragmas at configure time?
That sounds like a pretty nice idea. Even after going so far as to
edit my loc
Very cool do we need something like a LIBMESH_INCLUDE_NO_WARN_BEGIN and
LIBMESH_INCLUDE_NO_WARN_END that could be set to compiler specific #pragmas at
configure time?
Derek
On Jun 1, 2011, at 8:11 AM, Antonio Cervone wrote:
> you can specity to gcc that warnings coming from outside library
you can specity to gcc that warnings coming from outside library
should be ignored wrapping the include in a pragma
// Tell the compiler to ignore specific kind of warnings:
#pragma GCC diagnostic ignored "-Wunused-variable"
#pragma GCC diagnostic ignored "-Wunused-parameter"
#include
// Restor
On Tue, 31 May 2011, Kyunghoon Lee wrote:
/opt/local/include/mpicxx.h:386: warning: unused parameter ‘oldtype’
/opt/local/include/mpicxx.h:386: warning: unused parameter ‘keyval’
/opt/local/include/mpicxx.h:386: warning: unused parameter ‘ex’
/opt/local/include/mpicxx.h:386: warning: unused par
>> On Tue, May 31, 2011 at 1:08 PM, Kyunghoon Lee wrote:
>>> Hello,
>>>
>>> I'm trying to install libmesh on a MacOS X 10.6.7, which has a gcc-4.2
>>> compiler from Xcode 3.2.6. I had no trouble with compiling libmesh, but I
>>> got a seg fault error for the examples.
>>>
>>> First, I source
To avoid this... if you are not needing to compile any fortran then you can
just use the MPI that comes with OSX (OpenMP). Just set CC, CXX, etc to mpicc,
mpicxx etc for both PetsC and libMesh... and don't tell PetsC to download mpich.
Note that we don't typically work this way. We usually dow
On Tue, May 31, 2011 at 1:08 PM, Kyunghoon Lee wrote:
> Hello,
>
> I'm trying to install libmesh on a MacOS X 10.6.7, which has a gcc-4.2
> compiler from Xcode 3.2.6. I had no trouble with compiling libmesh, but I
> got a seg fault error for the examples.
>
> First, I source-compiled petsc with
Hello,
I'm trying to install libmesh on a MacOS X 10.6.7, which has a gcc-4.2 compiler
from Xcode 3.2.6. I had no trouble with compiling libmesh, but I got a seg
fault error for the examples.
First, I source-compiled petsc with the following configuration option:
export PETSC_DIR=$PWD
./conf
