On Nov 22, 2012, at 8:34 PM, "Kirk, Benjamin (JSC-EG311)" <[email protected]> wrote:
> I'll need a little more information than "it didn't work" - what are the > error messages? > > Another change is that we are strictly enforcing header prefixing, e.g. > > #include "libmesh/elem.h" This was the problem. It's fixed now. Thanks, Ata > > -Ben > > > > On Nov 22, 2012, at 6:00 PM, "Ataollah Mesgarnejad" <[email protected]> > wrote: > >> Thanks for the help, libMesh compiled nicely. However here is my dilemma: I >> used to include Make.common from libmesh_dir in my own code's Makefile and >> everything compiled easily however now I don't have any idea how to do this >> anymore? I tried Make.common in my install dir and it didn't work! Also I >> tried to compile several examples using the makefile in their folders and it >> didn't work. >> >> Happy thanksgiving again, >> Ata >> >> On Nov 21, 2012, at 3:24 PM, "Kirk, Benjamin (JSC-EG311)" >> <[email protected]> wrote: >> >>> Quickstart from an svn up: >>> >>> $ rm include/libmesh/*.h # in case there were any old symlinks - these are >>> now generated by default. >>> $ svn status # if this shows anything modified and you are not expecting >>> it, do 'svn revert -R .' >>> $ ./bootstrap >>> $ ./configure --prefix=/my/path/to/libmesh >>> $ make -jN # where N is your number of processors to speed up the build >>> $ make check # run the examples to make sure everything is fine >>> $ make install >>> $ make installcheck # optional, makes sure the install is behaving properly >>> >>> then point your build system to the install directory. >>> >>> That should work. If it does not please repot the error message, but also >>> try checking out a fresh copy of trunk - for example: >>> >>> $ svn co https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh >>> libmesh.fresh >>> >>> and try again and report the results. >>> >>> >>> If you want to use multiple methods, they can be installed in the same >>> place but need to be configured and built in separate directories. The >>> script ./contrib/bin/buildall.sh abstracts this, but the gist is >>> >>> $ mkdir dbg devel opt >>> $ cd dbg >>> $ ../configure --prefix=… --with-method=dbg >>> $ make && make install >>> $ cd ../opt >>> $ ../configure --prefix=… --with-method=opt >>> $ ... >>> >>> >>> >>> >>> >>> On Nov 21, 2012, at 1:34 PM, Ataollah Mesgarnejad <[email protected]> >>> wrote: >>> >>>> Dear all, >>>> >>>> I was wondering if someone can give me quick intro for the new make system >>>> ? I can't make heads nor tails of what's going on with autoconf. >>>> >>>> Happy thanksgiving, >>>> Ata >>>> ------------------------------------------------------------------------------ >>>> Monitor your physical, virtual and cloud infrastructure from a single >>>> web console. Get in-depth insight into apps, servers, databases, vmware, >>>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>>> Pricing starts from $795 for 25 servers or applications! >>>> http://p.sf.net/sfu/zoho_dev2dev_nov >>>> _______________________________________________ >>>> Libmesh-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >> ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
