Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

> From: harroontheg...@gmail.com > Date: Tue, 9 Aug 2016 13:19:07 -0700 > Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was > not declared in scope > To: jwpeter...@gmail.com > CC: marchy...@hotmail.com;

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

> From: harroontheg...@gmail.com > Date: Tue, 9 Aug 2016 13:33:15 -0700 > Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was > not declared in scope > To: marchy...@hotmail.com > CC: royst...@ices.utexas.edu;

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

Just incase I can just have my program in with the other examples to run it I was wondering how to view the output of the example files as well as what line to add to the config.ac file (Under the variable AC_CONFIG_FILES) to add a new example to libmesh. Also I clicked reply instead of reply all

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

>I ran make -n example-opt in the section of examples on eigenproblems_ex2, made a copy of eigenproblems_ex2, >changed the name of the original eigenproblems_ex2 to realeigenproblems_ex2, and put my .C file in the new folder called >eigenproblems_ex2 in , deleting the old .C file that was there (I

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

The header files are in usr/local/include but they are also in /opt/libmesh-1.0.0-rc1/include/libmesh. I think it is because the computer I'm using has two installations of libmesh, the libmesh-1.0.0 and libmesh-0.7.3.2. The Libmesh-1.0.0 was only recently downloaded by my professor/PI. I obtained

Re: [Libmesh-users] Renumbering mesh elements

Thank you for your answer. Your strategy worked perfectly. I ended up using the following block of code to renumber the mesh. // The mapping is stored in the vector new_to_old, where // new_to_old[elem_old_id] = elem_new_id. // Also _mesh.prepare_for_use is already called once because // it was

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

I accidentally sent that but I wasn't finished typing my email. If I use the output of make -n example-opt I would imagine that I need to have the appropriate object files in my directory (which I had in the eigenproblems_ex2 file (the copy I made)). Do I need them in the directory? If I don't

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

On Tue, Aug 9, 2016 at 1:54 PM, Harry Pearce wrote: > The program I ran wasn't in the libmesh directory when I ran it. I just > compiled it with: > > mpicxx -o HPeigenproblems_PZ_8_2_16_2 HPeigenproblems_PZ_8_2_16_2.C -lz > -Wl,-rpath,/usr/local/lib -L/usr/local/lib

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

The program I ran wasn't in the libmesh directory when I ran it. I just compiled it with: mpicxx -o HPeigenproblems_PZ_8_2_16_2 HPeigenproblems_PZ_8_2_16_2.C -lz -Wl,-rpath,/usr/local/lib -L/usr/local/lib -lmesh_opt -I/usr/local/include -pthread -I/usr/local/include -std=gnu++11 -O2

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

On Tue, Aug 9, 2016 at 11:35 AM, Harry Pearce wrote: > Thank you for your help so far. It looks like this problem is close to > being finished. Your recommendation of using #include "libmesh/foo.h" > worked for compiling the program (I used the full path for >

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

> From: harroontheg...@gmail.com > Date: Tue, 9 Aug 2016 10:35:47 -0700 > Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was > not declared in scope > To: marchy...@hotmail.com > CC: royst...@ices.utexas.edu;

Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not declared in scope

Thank you for your help so far. It looks like this problem is close to being finished. Your recommendation of using #include "libmesh/foo.h" worked for compiling the program (I used the full path for libmesh_nullptr.h in the include part and that fixed those errors) but now when I run the