Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Derek Gaston
Well... the trouble is that an Epetra_FEVector is _not_ an Epetra_Vector! (in the OO sense... as in it doesn't inherit from Epetra_Vector)... so I'm not sure if we'll run into trouble later on when we try to pass an Epetra_FEVector to something like NOX. One would hope that NOX expects an

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Roy Stogner
On Mon, 16 Jun 2008, John Peterson wrote: >> the petsc folks define __gierr and then the gcc people are apparently >> trying to use this same __gierr variable somewhere (I can't see >> exactly where at the moment but the error message alludes to it). I >> think this is petsc's fault because you

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Benjamin Kirk
> They are actually redefining "underscore." I have no clue why but > that can't be good programming practice. This is invigorating me to finish the Trilinos integration. It will be nice to have a functional alternative to solve linear systems on parallel platforms. Along these lines, Derek, an

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread John Peterson
On Mon, Jun 16, 2008 at 3:49 PM, John Peterson <[EMAIL PROTECTED]> wrote: > On Mon, Jun 16, 2008 at 3:35 PM, John Peterson <[EMAIL PROTECTED]> wrote: >> On Mon, Jun 16, 2008 at 3:35 PM, John Peterson <[EMAIL PROTECTED]> wrote: >>> On Mon, Jun 16, 2008 at 1:50 PM, Roy Stogner <[EMAIL PROTECTED]> wro

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread John Peterson
On Mon, Jun 16, 2008 at 3:35 PM, John Peterson <[EMAIL PROTECTED]> wrote: > On Mon, Jun 16, 2008 at 3:35 PM, John Peterson <[EMAIL PROTECTED]> wrote: >> On Mon, Jun 16, 2008 at 1:50 PM, Roy Stogner <[EMAIL PROTECTED]> wrote: >>> >>> Vikram just ran into this ugly problem while trying to get Ben's c

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Roy Stogner
On Mon, 16 Jun 2008, John Peterson wrote: > Crap, nevermind. If you include tr1/unordered_map *before* > petscoptions.h it goes away. Thanks; that's exactly the fix we needed. --- Roy - Check out the new SourceForge.net Ma

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread John Peterson
On Mon, Jun 16, 2008 at 3:35 PM, John Peterson <[EMAIL PROTECTED]> wrote: > On Mon, Jun 16, 2008 at 1:50 PM, Roy Stogner <[EMAIL PROTECTED]> wrote: >> >> Vikram just ran into this ugly problem while trying to get Ben's code >> up to speed with SVN libMesh. Here's a minimal test case: >> >> >> test

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread John Peterson
On Mon, Jun 16, 2008 at 1:50 PM, Roy Stogner <[EMAIL PROTECTED]> wrote: > > Vikram just ran into this ugly problem while trying to get Ben's code > up to speed with SVN libMesh. Here's a minimal test case: > > > test.C: > > extern "C" { > #include "petscoptions.h" > } > #include > > > > That's it

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Benjamin Kirk
No issues under CentOS-5.1 with gcc-4.1.1. On 6/16/08 2:20 PM, "Derek Gaston" <[EMAIL PROTECTED]> wrote: > No problems here on OSX with gcc 4.0.1. Nor do I have a problem on > our cluster here running Suse with gcc 4.1.2. > > Derek > > > On Jun 16, 2008, at 12:50 PM, Roy Stogner wrote: > >>

Re: [Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Derek Gaston
No problems here on OSX with gcc 4.0.1. Nor do I have a problem on our cluster here running Suse with gcc 4.1.2. Derek On Jun 16, 2008, at 12:50 PM, Roy Stogner wrote: > > Vikram just ran into this ugly problem while trying to get Ben's code > up to speed with SVN libMesh. Here's a minimal

[Libmesh-devel] Odd C++/PETSc problem

2008-06-16 Thread Roy Stogner
Vikram just ran into this ugly problem while trying to get Ben's code up to speed with SVN libMesh. Here's a minimal test case: test.C: extern "C" { #include "petscoptions.h" } #include That's it. Trying to compile this breaks in the CFDLab in all sorts of fun ways. We can work around it