This is the error.

 CXX      src/apps/getpot_parse_opt-getpot_parse.o
  CXXLD    getpot_parse-opt
  CXX      src/apps/meshtool_opt-meshtool.o
  CXXLD    meshtool-opt
Undefined symbols for architecture x86_64:
  "Hilbert::coordsToIndex(CFixBitVec const*, int, int, CBigBitVec&)", 
referenced from:
      Hilbert::HilbertIndices (anonymous 
namespace)::get_hilbert_index<libMesh::Node>(libMesh::Node const*, 
libMesh::MeshTools::BoundingBox const&) in 
libmesh_opt.a(libmesh_opt_la-mesh_communication_global_indices.o)
      Hilbert::HilbertIndices (anonymous 
namespace)::get_hilbert_index<libMesh::Elem>(libMesh::Elem const*, 
libMesh::MeshTools::BoundingBox const&) in 
libmesh_opt.a(libmesh_opt_la-mesh_communication_global_indices.o)
      (anonymous namespace)::get_hilbert_index(libMesh::Point const&, 
libMesh::MeshTools::BoundingBox const&) in 
libmesh_opt.a(libmesh_opt_la-mesh_communication_global_indices.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [meshtool-opt] Error 1
make: *** [all-recursive] Error 1

The compilation seems to be alright. Roy, is this what you meant?

digihabia:libmesh ihabia$ nm 
src/mesh/libmesh_opt_la-mesh_communication_global_indices.o | grep coordsToIndex
                 U __ZN7Hilbert13coordsToIndexEPK10CFixBitVeciiR10CBigBitVec

digihabia:libmesh ihabia$ nm contrib/libHilbert/src/libopt_la-Hilbert.o | grep 
coordsToIndex
0000000000000100 T __ZN7Hilbert13coordsToIndexEPK10CBigBitVeciiRS0_
0000000000008fa8 S __ZN7Hilbert13coordsToIndexEPK10CBigBitVeciiRS0_.eh
0000000000000080 T __ZN7Hilbert13coordsToIndexEPK10CFixBitVeciiR10CBigBitVec
0000000000008f08 S __ZN7Hilbert13coordsToIndexEPK10CFixBitVeciiR10CBigBitVec.eh
0000000000000000 T __ZN7Hilbert13coordsToIndexEPK10CFixBitVeciiRS0_
0000000000008e68 S __ZN7Hilbert13coordsToIndexEPK10CFixBitVeciiRS0_.eh
0000000000002300 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVec10CFixBitVecS1_EEvPKT_iiRT0_Pi
0000000000009238 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVec10CFixBitVecS1_EEvPKT_iiRT0_Pi.eh
0000000000002e90 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVec10CFixBitVecS2_EEvPKT_iiRT0_Pi
0000000000009300 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVec10CFixBitVecS2_EEvPKT_iiRT0_Pi.eh
0000000000002c00 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVecS1_10CFixBitVecEEvPKT_iiRT0_Pi
00000000000092d0 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVecS1_10CFixBitVecEEvPKT_iiRT0_Pi.eh
00000000000020a0 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVecS1_S1_EEvPKT_iiRT0_Pi
0000000000009200 S 
__ZN7Hilbert14_coordsToIndexI10CBigBitVecS1_S1_EEvPKT_iiRT0_Pi.eh
00000000000062c0 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVec10CBigBitVecS1_EEvPKT_iiRT0_Pi
0000000000009600 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVec10CBigBitVecS1_EEvPKT_iiRT0_Pi.eh
00000000000057c0 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVec10CBigBitVecS2_EEvPKT_iiRT0_Pi
0000000000009530 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVec10CBigBitVecS2_EEvPKT_iiRT0_Pi.eh
0000000000005a20 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVecS1_10CBigBitVecEEvPKT_iiRT0_Pi
0000000000009568 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVecS1_10CBigBitVecEEvPKT_iiRT0_Pi.eh
0000000000006550 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVecS1_S1_EEvPKT_iiRT0_Pi
0000000000009630 S 
__ZN7Hilbert14_coordsToIndexI10CFixBitVecS1_S1_EEvPKT_iiRT0_Pi.eh

> 
> Can you do whatever the Apple equivalent of nm is on your
> libcontrib_opt and grep for coordsToIndex to see what's there?  I'm
> not sure whether that function isn't getting properly compiled into
> your libcontrib or whether your libcontrib isn't getting properly
> linked into libMesh apps.
> ---
> Roy


------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to