Yes, I am configuring and building libmesh without using the MOOSE script. After reading your previous message, I decided to redo the procedure. Here is what I did: I created a directory called "build" inside the libmesh folder. I provided the path of this build directory as the --prefix argument for the configure script. After the configure step, I entered the make command. I now get the following error message:
../../tests/driver.C:4:29: fatal error: libmesh/libmesh.h: No such file or directory compilation terminated. make[1]: *** [unit_tests_dbg-driver.o] Error 1 make[1]: Leaving directory `/home/moose/libmesh/build/tests' make: *** [all-recursive] Error 1 The file driver.C has a line : #include <libmesh/libmesh.h> There is no file libmesh.h in the location libmesh/build/include/libmesh. What am I doing wrong? Best regards, Nikhil On Thu, Jun 7, 2018 at 5:08 PM, John Peterson <jwpeter...@gmail.com> wrote: > > > On Thu, Jun 7, 2018 at 8:59 AM, Nikhil Vaidya <nikhilvaidy...@gmail.com> > wrote: > >> Hi John, >> >> Yes, I am using MOOSE, but this particular installation is not within >> MOOSE. This particular installation is being done outside the MOOSE >> directory. I just checked the $LIBMESH_DIR variable and it is unset. What >> else can potentially cause this? >> > > So you are configuring and building libmesh without using the MOOSE script? > > What options did you pass to configure? In particular, did you specify a > --prefix that would install directly into the libmesh source tree? > > -- > John > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
