On Mon, Sep 13, 2010 at 10:03 AM, Dec, John A. (LARC-D206) <[email protected]> wrote: > Ben, > > Here are the compile and link lines as well as the link errors. I modified > makefile from one of the examples and it references the Make.Common file that > gets generated from ./configure when setting up the library. I recently > pulled a more current version of libMesh from the svn trunk on 8/24/2010 > version 3919 I believe. This is strange since it links without any problems > in opt mode.
Maybe check and see if those undefined references are really undefined... Something like: $ nm /path/to/libmesh.a | grep compute_map | grep FEBase may produce lots of lines of output, but at least one line should have a symbol other than "U" in the second column, for example on an OS X 10.5 system with a static library I get 00004fd0 T __ZN7libMesh6FEBase11compute_mapERKSt6vectorIdSaIdEEPKNS_4ElemE And on a linux system with a dynamic libmesh.so: 000000000035ccda T _ZN7libMesh6FEBase11compute_mapERKSt6vectorIdSaIdEEPKNS_4ElemE If these lines aren't found then it may be something with the compile step, if they are found, then for some reason the linker is not locating them. -- John ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
