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 the compile line by typing in:
`libmesh-config --cxx` -o foo foo.C `libmesh-config --cxxflags --include --ldflags --libs` which I found out about from the libmesh website section "installation". On Tue, Aug 9, 2016 at 1:00 PM, John Peterson <jwpeter...@gmail.com> wrote: > > > On Tue, Aug 9, 2016 at 1:54 PM, Harry Pearce <harroontheg...@gmail.com> > 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 -lmesh_opt -I/usr/local/include >> -pthread -I/usr/local/include -std=gnu++11 -O2 -felide-constructors >> -funroll-loops -fstrict-aliasing -Wdisabled-optimization -fopenmp >> > > > How did you arrive at this compile line? I don't see any include > directives for libmesh, PETSc, SLEPc, or anything else, unless they are all > installed directly in /usr/local/include? > > -- > John > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
