From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-06 20:45:58
|
Hi, I am a new user of Libmesh, and I tried to install it in Unix Sun = Solaris. When I compile it, it runs ok till to the /contrib/parmetis/Lib = subdir. The error looks like: --- Building Parmetis ------------------------ make[2]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' Compiling C (in optimized mode) adrivers.c... In file included from parmetis.h:22, from adrivers.c:16: stdheaders.h:25:17: mpi.h: No such file or directory In file included from parmetis.h:30, from adrivers.c:16: struct.h:263: error: parse error before "MPI_Comm" struct.h:263: warning: no semicolon at end of struct or union struct.h:264: warning: data definition has no type or storage class struct.h:265: error: parse error before "sreq" struct.h:266: warning: data definition has no type or storage class struct.h:267: error: parse error before "statuses" struct.h:267: warning: data definition has no type or storage class struct.h:268: error: parse error before "status" struct.h:268: warning: data definition has no type or storage class struct.h:274: error: parse error before '}' token In file included from parmetis.h:32, from adrivers.c:16: proto.h:16: error: parse error before "MPI_Comm" proto.h:19: error: parse error before "MPI_Comm" proto.h:22: error: parse error before "MPI_Comm" proto.h:23: error: parse error before "MPI_Comm" proto.h:75: error: parse error before "MPI_Comm" proto.h:78: error: parse error before "MPI_Comm" proto.h:146: error: parse error before "MPI_Comm" proto.h:152: error: parse error before "MPI_Comm" proto.h:155: error: parse error before "MPI_Comm" proto.h:164: error: parse error before "MPI_Comm" proto.h:167: error: parse error before "MPI_Comm" proto.h:313: error: parse error before "MPI_Comm" proto.h:333: error: parse error before "MPI_Comm" proto.h:334: error: parse error before "MPI_Comm" proto.h:336: error: parse error before "MPI_Comm" proto.h:337: error: parse error before "MPI_Comm" proto.h:339: error: parse error before "MPI_Comm" proto.h:340: error: parse error before "MPI_Comm" proto.h:341: error: parse error before "MPI_Comm" proto.h:342: error: parse error before "MPI_Comm" proto.h:344: error: parse error before "MPI_Comm" proto.h:345: error: parse error before "MPI_Comm" proto.h:347: error: parse error before "MPI_Comm" proto.h:348: error: parse error before "MPI_Comm" proto.h:349: error: parse error before "MPI_Comm" proto.h:350: error: parse error before "MPI_Comm" proto.h:351: error: parse error before "MPI_Comm" proto.h:352: error: parse error before "MPI_Comm" proto.h:354: error: parse error before "MPI_Comm" proto.h:355: error: parse error before "MPI_Comm" proto.h:378: error: parse error before "MPI_Comm" proto.h:380: error: parse error before "MPI_Comm" proto.h:381: error: parse error before "MPI_Comm" proto.h:383: error: parse error before "MPI_Comm" proto.h:387: error: parse error before "MPI_Comm" proto.h:388: error: parse error before "MPI_Comm" proto.h:389: error: parse error before "MPI_Comm" proto.h:392: error: parse error before "MPI_Comm" proto.h:395: error: parse error before "MPI_Comm" proto.h:396: error: parse error before "MPI_Comm" proto.h:397: error: parse error before "MPI_Comm" proto.h:398: error: parse error before "MPI_Comm" proto.h:402: error: parse error before "MPI_Comm" proto.h:405: error: parse error before "MPI_Comm" adrivers.c: In function `Adaptive_Partition__': adrivers.c:35: error: dereferencing pointer to incomplete type adrivers.c:40: error: dereferencing pointer to incomplete type adrivers.c:40: error: dereferencing pointer to incomplete type adrivers.c:40: error: dereferencing pointer to incomplete type adrivers.c:42: error: dereferencing pointer to incomplete type adrivers.c:42: error: dereferencing pointer to incomplete type adrivers.c:46: error: dereferencing pointer to incomplete type adrivers.c:58: error: dereferencing pointer to incomplete type adrivers.c:61: error: dereferencing pointer to incomplete type adrivers.c:63: error: dereferencing pointer to incomplete type adrivers.c:66: error: dereferencing pointer to incomplete type adrivers.c:69: error: dereferencing pointer to incomplete type adrivers.c:83: error: dereferencing pointer to incomplete type adrivers.c:113: error: dereferencing pointer to incomplete type adrivers.c:115: error: dereferencing pointer to incomplete type adrivers.c:118: error: dereferencing pointer to incomplete type adrivers.c:121: error: dereferencing pointer to incomplete type make[2]: *** [adrivers.sparc-sun-solaris2.8.o] Error 1 make[2]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' make[1]: *** [all] Error 2 make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib' make: *** = [/users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.8_opt/libme= sh.so] Error 2 Could somebody tell me what I should change for the compileing? Thanks |
From: Ahmed EL-S. <els...@mc...> - 2004-03-06 22:15:59
|
Try ./configure --disable-parmetis --disable-petsc --disable-mpi --disable-shared make METHOD=dbg make METHOD=dbg run_examples Ahmed -- "No great thing is created suddenly." Epictetus ************************************************** Ahmed ElSheikh <els...@mc...> PhD Candidate, Department of Civil Engineering McMaster University 1280 Main Street West Hamilton, Ontario, L8S 4L7, Canada. Fax : (905) 529-9688 Cellular: (905) 920-9204 Work : (905) 525-9140 EXT. 22044 ************************************************** Yuna wrote: > Hi, I am a new user of Libmesh, and I tried to install it in Unix > Sun Solaris. When I compile it, it runs ok till to the > /contrib/parmetis/Lib subdir. The error looks like: --- Building > Parmetis ------------------------ > make[2]: Entering directory > `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' > Compiling C (in optimized mode) adrivers.c... > In file included from parmetis.h:22, > from adrivers.c:16: > stdheaders.h:25:17: mpi.h: No such file or directory > In file included from parmetis.h:30, > from adrivers.c:16: > struct.h:263: error: parse error before "MPI_Comm" > struct.h:263: warning: no semicolon at end of struct or union > struct.h:264: warning: data definition has no type or storage class > struct.h:265: error: parse error before "sreq" > struct.h:266: warning: data definition has no type or storage class > struct.h:267: error: parse error before "statuses" > struct.h:267: warning: data definition has no type or storage class > struct.h:268: error: parse error before "status" > struct.h:268: warning: data definition has no type or storage class > struct.h:274: error: parse error before '}' token > In file included from parmetis.h:32, > from adrivers.c:16: > proto.h:16: error: parse error before "MPI_Comm" > proto.h:19: error: parse error before "MPI_Comm" > proto.h:22: error: parse error before "MPI_Comm" > proto.h:23: error: parse error before "MPI_Comm" > proto.h:75: error: parse error before "MPI_Comm" > proto.h:78: error: parse error before "MPI_Comm" > proto.h:146: error: parse error before "MPI_Comm" > proto.h:152: error: parse error before "MPI_Comm" > proto.h:155: error: parse error before "MPI_Comm" > proto.h:164: error: parse error before "MPI_Comm" > proto.h:167: error: parse error before "MPI_Comm" > proto.h:313: error: parse error before "MPI_Comm" > proto.h:333: error: parse error before "MPI_Comm" > proto.h:334: error: parse error before "MPI_Comm" > proto.h:336: error: parse error before "MPI_Comm" > proto.h:337: error: parse error before "MPI_Comm" > proto.h:339: error: parse error before "MPI_Comm" > proto.h:340: error: parse error before "MPI_Comm" > proto.h:341: error: parse error before "MPI_Comm" > proto.h:342: error: parse error before "MPI_Comm" > proto.h:344: error: parse error before "MPI_Comm" > proto.h:345: error: parse error before "MPI_Comm" > proto.h:347: error: parse error before "MPI_Comm" > proto.h:348: error: parse error before "MPI_Comm" > proto.h:349: error: parse error before "MPI_Comm" > proto.h:350: error: parse error before "MPI_Comm" > proto.h:351: error: parse error before "MPI_Comm" > proto.h:352: error: parse error before "MPI_Comm" > proto.h:354: error: parse error before "MPI_Comm" > proto.h:355: error: parse error before "MPI_Comm" > proto.h:378: error: parse error before "MPI_Comm" > proto.h:380: error: parse error before "MPI_Comm" > proto.h:381: error: parse error before "MPI_Comm" > proto.h:383: error: parse error before "MPI_Comm" > proto.h:387: error: parse error before "MPI_Comm" > proto.h:388: error: parse error before "MPI_Comm" > proto.h:389: error: parse error before "MPI_Comm" > proto.h:392: error: parse error before "MPI_Comm" > proto.h:395: error: parse error before "MPI_Comm" > proto.h:396: error: parse error before "MPI_Comm" > proto.h:397: error: parse error before "MPI_Comm" > proto.h:398: error: parse error before "MPI_Comm" > proto.h:402: error: parse error before "MPI_Comm" > proto.h:405: error: parse error before "MPI_Comm" > adrivers.c: In function `Adaptive_Partition__': > adrivers.c:35: error: dereferencing pointer to incomplete type > adrivers.c:40: error: dereferencing pointer to incomplete type > adrivers.c:40: error: dereferencing pointer to incomplete type > adrivers.c:40: error: dereferencing pointer to incomplete type > adrivers.c:42: error: dereferencing pointer to incomplete type > adrivers.c:42: error: dereferencing pointer to incomplete type > adrivers.c:46: error: dereferencing pointer to incomplete type > adrivers.c:58: error: dereferencing pointer to incomplete type > adrivers.c:61: error: dereferencing pointer to incomplete type > adrivers.c:63: error: dereferencing pointer to incomplete type > adrivers.c:66: error: dereferencing pointer to incomplete type > adrivers.c:69: error: dereferencing pointer to incomplete type > adrivers.c:83: error: dereferencing pointer to incomplete type > adrivers.c:113: error: dereferencing pointer to incomplete type > adrivers.c:115: error: dereferencing pointer to incomplete type > adrivers.c:118: error: dereferencing pointer to incomplete type > adrivers.c:121: error: dereferencing pointer to incomplete type > make[2]: *** [adrivers.sparc-sun-solaris2.8.o] Error 1 > make[2]: Leaving directory > `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' > make[1]: *** [all] Error 2 > make[1]: Leaving directory > `/users/hyuna/myResearch/libmesh-0.4.2/contrib' > make: *** > [/users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.8_opt/libmesh.so] > Error 2Could somebody tell me what I should change for the > compileing? Thanks |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-06 23:37:12
|
Hi, Thanks for your help. I have compiled the libmesh library successfully = except some warning. When I go to run the examples, I got the following errors like: make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples' make[2]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' Compiling C++ (in debug mode) ex1.C... Linking ex1... Undefined first referenced symbol in file xdr_u_short = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdr_cxx.sparc-sun-solaris2.9.g.o) xdrstdio_create = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) xdr_double = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) xdr_u_int = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) xdr_float = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdr_cxx.sparc-sun-solaris2.9.g.o) xdr_short = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdr_cxx.sparc-sun-solaris2.9.g.o) xdr_string = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) xdr_int = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) xdr_vector = /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.9_dbg/libmes= h.a(xdrIO.sparc-sun-solaris2.9.g.o) ld: fatal: Symbol referencing errors. No output written to ex1 collect2: ld returned 1 exit status make[2]: *** [ex1] Error 1 make[2]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' make[1]: *** [run] Error 2 make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples' make: *** [run_examples] Error 2 So could you give me more help? ----- Original Message -----=20 From: Ahmed EL-Sheikh=20 To: lib...@li...=20 Cc: Yuna=20 Sent: Saturday, March 06, 2004 5:59 PM Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in = Solorias Try=20 ./configure --disable-parmetis --disable-petsc --disable-mpi = --disable-shared=20 make METHOD=3Ddbg=20 make METHOD=3Ddbg run_examples=20 Ahmed=20 --=20 "No great thing is created suddenly." Epictetus=20 **************************************************=20 Ahmed ElSheikh <els...@mc...>=20 PhD Candidate, Department of Civil Engineering=20 McMaster University=20 1280 Main Street West=20 Hamilton, Ontario, L8S 4L7, Canada.=20 Fax : (905) 529-9688=20 Cellular: (905) 920-9204=20 Work : (905) 525-9140 EXT. 22044=20 **************************************************=20 Yuna wrote:=20 Hi, I am a new user of Libmesh, and I tried to install it in Unix = Sun Solaris. When I compile it, it runs ok till to the = /contrib/parmetis/Lib subdir. The error looks like: --- Building = Parmetis ------------------------=20 make[2]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib'=20 Compiling C (in optimized mode) adrivers.c...=20 In file included from parmetis.h:22,=20 from adrivers.c:16:=20 stdheaders.h:25:17: mpi.h: No such file or directory=20 In file included from parmetis.h:30,=20 from adrivers.c:16:=20 struct.h:263: error: parse error before "MPI_Comm"=20 struct.h:263: warning: no semicolon at end of struct or union=20 struct.h:264: warning: data definition has no type or storage class=20 struct.h:265: error: parse error before "sreq"=20 struct.h:266: warning: data definition has no type or storage class=20 struct.h:267: error: parse error before "statuses"=20 struct.h:267: warning: data definition has no type or storage class=20 struct.h:268: error: parse error before "status"=20 struct.h:268: warning: data definition has no type or storage class=20 struct.h:274: error: parse error before '}' token=20 In file included from parmetis.h:32,=20 from adrivers.c:16:=20 proto.h:16: error: parse error before "MPI_Comm"=20 proto.h:19: error: parse error before "MPI_Comm"=20 proto.h:22: error: parse error before "MPI_Comm"=20 proto.h:23: error: parse error before "MPI_Comm"=20 proto.h:75: error: parse error before "MPI_Comm"=20 proto.h:78: error: parse error before "MPI_Comm"=20 proto.h:146: error: parse error before "MPI_Comm"=20 proto.h:152: error: parse error before "MPI_Comm"=20 proto.h:155: error: parse error before "MPI_Comm"=20 proto.h:164: error: parse error before "MPI_Comm"=20 proto.h:167: error: parse error before "MPI_Comm"=20 proto.h:313: error: parse error before "MPI_Comm"=20 proto.h:333: error: parse error before "MPI_Comm"=20 proto.h:334: error: parse error before "MPI_Comm"=20 proto.h:336: error: parse error before "MPI_Comm"=20 proto.h:337: error: parse error before "MPI_Comm"=20 proto.h:339: error: parse error before "MPI_Comm"=20 proto.h:340: error: parse error before "MPI_Comm"=20 proto.h:341: error: parse error before "MPI_Comm"=20 proto.h:342: error: parse error before "MPI_Comm"=20 proto.h:344: error: parse error before "MPI_Comm"=20 proto.h:345: error: parse error before "MPI_Comm"=20 proto.h:347: error: parse error before "MPI_Comm"=20 proto.h:348: error: parse error before "MPI_Comm"=20 proto.h:349: error: parse error before "MPI_Comm"=20 proto.h:350: error: parse error before "MPI_Comm"=20 proto.h:351: error: parse error before "MPI_Comm"=20 proto.h:352: error: parse error before "MPI_Comm"=20 proto.h:354: error: parse error before "MPI_Comm"=20 proto.h:355: error: parse error before "MPI_Comm"=20 proto.h:378: error: parse error before "MPI_Comm"=20 proto.h:380: error: parse error before "MPI_Comm"=20 proto.h:381: error: parse error before "MPI_Comm"=20 proto.h:383: error: parse error before "MPI_Comm"=20 proto.h:387: error: parse error before "MPI_Comm"=20 proto.h:388: error: parse error before "MPI_Comm"=20 proto.h:389: error: parse error before "MPI_Comm"=20 proto.h:392: error: parse error before "MPI_Comm"=20 proto.h:395: error: parse error before "MPI_Comm"=20 proto.h:396: error: parse error before "MPI_Comm"=20 proto.h:397: error: parse error before "MPI_Comm"=20 proto.h:398: error: parse error before "MPI_Comm"=20 proto.h:402: error: parse error before "MPI_Comm"=20 proto.h:405: error: parse error before "MPI_Comm"=20 adrivers.c: In function `Adaptive_Partition__':=20 adrivers.c:35: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:42: error: dereferencing pointer to incomplete type=20 adrivers.c:42: error: dereferencing pointer to incomplete type=20 adrivers.c:46: error: dereferencing pointer to incomplete type=20 adrivers.c:58: error: dereferencing pointer to incomplete type=20 adrivers.c:61: error: dereferencing pointer to incomplete type=20 adrivers.c:63: error: dereferencing pointer to incomplete type=20 adrivers.c:66: error: dereferencing pointer to incomplete type=20 adrivers.c:69: error: dereferencing pointer to incomplete type=20 adrivers.c:83: error: dereferencing pointer to incomplete type=20 adrivers.c:113: error: dereferencing pointer to incomplete type=20 adrivers.c:115: error: dereferencing pointer to incomplete type=20 adrivers.c:118: error: dereferencing pointer to incomplete type=20 adrivers.c:121: error: dereferencing pointer to incomplete type=20 make[2]: *** [adrivers.sparc-sun-solaris2.8.o] Error 1=20 make[2]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib'=20 make[1]: *** [all] Error 2=20 make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib'=20 make: *** = [/users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.8_opt/libme= sh.so] Error 2Could somebody tell me what I should change for the = compileing? Thanks |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-07 00:22:01
|
Hi, I try to run example again. I go to the directory /examples, and run = "make METHOD=3Ddbg", all of examples can be compied, but no any = executable files were created. Look the compile informations: ---------------------------------------------- --------- Building Example Programs ---------- ---------------------------------------------- make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' Compiling C++ (in debug mode) ex1.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex2' Compiling C++ (in debug mode) ex2.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex2' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex3' Compiling C++ (in debug mode) ex3.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex3' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex4' Compiling C++ (in debug mode) ex4.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex4' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex5' Compiling C++ (in debug mode) ex5.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex5' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex6' Compiling C++ (in debug mode) ex6.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex6' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex7' Compiling C++ (in debug mode) ex7.C... ex7.C: In function `void assemble_helmholtz(EquationSystems&, const=20 std::string&)': ex7.C:261: warning: unused parameter `EquationSystems&es' ex7.C:261: warning: unused parameter `const std::string&system_name' ex7.C: In function `void add_M_C_K_helmholtz(EquationSystems&, const=20 std::string&)': ex7.C:505: warning: unused parameter `EquationSystems&es' ex7.C:505: warning: unused parameter `const std::string&system_name' make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex7' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex8' Compiling C++ (in debug mode) ex8.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex8' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex9' Compiling C++ (in debug mode) ex9.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex9' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex10' Compiling C++ (in debug mode) ex10.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex10' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex11' Compiling C++ (in debug mode) ex11.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex11' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex12' Compiling C++ (in debug mode) ex12.C... make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex12' make[1]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex13' Compiling C++ (in debug mode) ex13.C... ex13.C: In function `void assemble_stokes(EquationSystems&, const = std::string&) ': ex13.C:350: warning: unused variable `const Real time' make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex13' ---------------------------------------------- ------- Done Building Example Programs ------- ---------------------------------------------- So what does this mean? Yuna ----- Original Message -----=20 From: Ahmed EL-Sheikh=20 To: lib...@li...=20 Cc: Yuna=20 Sent: Saturday, March 06, 2004 5:59 PM Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in = Solorias Try=20 ./configure --disable-parmetis --disable-petsc --disable-mpi = --disable-shared=20 make METHOD=3Ddbg=20 make METHOD=3Ddbg run_examples=20 Ahmed=20 --=20 "No great thing is created suddenly." Epictetus=20 **************************************************=20 Ahmed ElSheikh <els...@mc...>=20 PhD Candidate, Department of Civil Engineering=20 McMaster University=20 1280 Main Street West=20 Hamilton, Ontario, L8S 4L7, Canada.=20 Fax : (905) 529-9688=20 Cellular: (905) 920-9204=20 Work : (905) 525-9140 EXT. 22044=20 **************************************************=20 Yuna wrote:=20 Hi, I am a new user of Libmesh, and I tried to install it in Unix = Sun Solaris. When I compile it, it runs ok till to the = /contrib/parmetis/Lib subdir. The error looks like: --- Building = Parmetis ------------------------=20 make[2]: Entering directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib'=20 Compiling C (in optimized mode) adrivers.c...=20 In file included from parmetis.h:22,=20 from adrivers.c:16:=20 stdheaders.h:25:17: mpi.h: No such file or directory=20 In file included from parmetis.h:30,=20 from adrivers.c:16:=20 struct.h:263: error: parse error before "MPI_Comm"=20 struct.h:263: warning: no semicolon at end of struct or union=20 struct.h:264: warning: data definition has no type or storage class=20 struct.h:265: error: parse error before "sreq"=20 struct.h:266: warning: data definition has no type or storage class=20 struct.h:267: error: parse error before "statuses"=20 struct.h:267: warning: data definition has no type or storage class=20 struct.h:268: error: parse error before "status"=20 struct.h:268: warning: data definition has no type or storage class=20 struct.h:274: error: parse error before '}' token=20 In file included from parmetis.h:32,=20 from adrivers.c:16:=20 proto.h:16: error: parse error before "MPI_Comm"=20 proto.h:19: error: parse error before "MPI_Comm"=20 proto.h:22: error: parse error before "MPI_Comm"=20 proto.h:23: error: parse error before "MPI_Comm"=20 proto.h:75: error: parse error before "MPI_Comm"=20 proto.h:78: error: parse error before "MPI_Comm"=20 proto.h:146: error: parse error before "MPI_Comm"=20 proto.h:152: error: parse error before "MPI_Comm"=20 proto.h:155: error: parse error before "MPI_Comm"=20 proto.h:164: error: parse error before "MPI_Comm"=20 proto.h:167: error: parse error before "MPI_Comm"=20 proto.h:313: error: parse error before "MPI_Comm"=20 proto.h:333: error: parse error before "MPI_Comm"=20 proto.h:334: error: parse error before "MPI_Comm"=20 proto.h:336: error: parse error before "MPI_Comm"=20 proto.h:337: error: parse error before "MPI_Comm"=20 proto.h:339: error: parse error before "MPI_Comm"=20 proto.h:340: error: parse error before "MPI_Comm"=20 proto.h:341: error: parse error before "MPI_Comm"=20 proto.h:342: error: parse error before "MPI_Comm"=20 proto.h:344: error: parse error before "MPI_Comm"=20 proto.h:345: error: parse error before "MPI_Comm"=20 proto.h:347: error: parse error before "MPI_Comm"=20 proto.h:348: error: parse error before "MPI_Comm"=20 proto.h:349: error: parse error before "MPI_Comm"=20 proto.h:350: error: parse error before "MPI_Comm"=20 proto.h:351: error: parse error before "MPI_Comm"=20 proto.h:352: error: parse error before "MPI_Comm"=20 proto.h:354: error: parse error before "MPI_Comm"=20 proto.h:355: error: parse error before "MPI_Comm"=20 proto.h:378: error: parse error before "MPI_Comm"=20 proto.h:380: error: parse error before "MPI_Comm"=20 proto.h:381: error: parse error before "MPI_Comm"=20 proto.h:383: error: parse error before "MPI_Comm"=20 proto.h:387: error: parse error before "MPI_Comm"=20 proto.h:388: error: parse error before "MPI_Comm"=20 proto.h:389: error: parse error before "MPI_Comm"=20 proto.h:392: error: parse error before "MPI_Comm"=20 proto.h:395: error: parse error before "MPI_Comm"=20 proto.h:396: error: parse error before "MPI_Comm"=20 proto.h:397: error: parse error before "MPI_Comm"=20 proto.h:398: error: parse error before "MPI_Comm"=20 proto.h:402: error: parse error before "MPI_Comm"=20 proto.h:405: error: parse error before "MPI_Comm"=20 adrivers.c: In function `Adaptive_Partition__':=20 adrivers.c:35: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:40: error: dereferencing pointer to incomplete type=20 adrivers.c:42: error: dereferencing pointer to incomplete type=20 adrivers.c:42: error: dereferencing pointer to incomplete type=20 adrivers.c:46: error: dereferencing pointer to incomplete type=20 adrivers.c:58: error: dereferencing pointer to incomplete type=20 adrivers.c:61: error: dereferencing pointer to incomplete type=20 adrivers.c:63: error: dereferencing pointer to incomplete type=20 adrivers.c:66: error: dereferencing pointer to incomplete type=20 adrivers.c:69: error: dereferencing pointer to incomplete type=20 adrivers.c:83: error: dereferencing pointer to incomplete type=20 adrivers.c:113: error: dereferencing pointer to incomplete type=20 adrivers.c:115: error: dereferencing pointer to incomplete type=20 adrivers.c:118: error: dereferencing pointer to incomplete type=20 adrivers.c:121: error: dereferencing pointer to incomplete type=20 make[2]: *** [adrivers.sparc-sun-solaris2.8.o] Error 1=20 make[2]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib'=20 make[1]: *** [all] Error 2=20 make[1]: Leaving directory = `/users/hyuna/myResearch/libmesh-0.4.2/contrib'=20 make: *** = [/users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.8_opt/libme= sh.so] Error 2Could somebody tell me what I should change for the = compileing? Thanks |
From: John P. <pet...@cf...> - 2004-03-07 02:12:38
|
Yuna writes: > Hi, > > I try to run example again. I go to the directory /examples, and > run "make METHOD=dbg", all of examples can be compied, but no any > executable files were created. Look the compile informations: So > what does this mean? For some reason it's not linking correctly. All the error messages are coming from the xdr libraries, which is strange since xdr came from Sun! -John |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-07 02:26:04
|
Yes, I use the Unix Sun compiler. When I run make METHOD=dbg, it will create some files like xdrIO.C, xdr_cxx.C, xdrIO.sparc-sun-solaris2.9.g.o... in the src/util directory. Do you have any other ways to link the library. Others, PETSc is installed in my unix system, how can I make configure to find it? Thanks a lot. ----- Original Message ----- From: "John Peterson" <pet...@cf...> To: "Yuna" <hyuna@CLEMSON.EDU> Cc: "Ahmed EL-Sheikh" <els...@mc...>; <lib...@li...> Sent: Saturday, March 06, 2004 8:57 PM Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > Yuna writes: > > Hi, > > > > I try to run example again. I go to the directory /examples, and > > run "make METHOD=dbg", all of examples can be compied, but no any > > executable files were created. Look the compile informations: So > > what does this mean? > For some reason it's not linking correctly. All the error messages are > coming from the xdr libraries, which is strange since xdr came from Sun! > > -John |
From: Ahmed E. <els...@mc...> - 2004-03-07 04:27:11
|
Hi, As in the source code documentation, XDR is a platform-independent binary I/O system. You have to check the linker options, but it is tricky :) As a temporary solution till you get a complete answer, add --disable-xdr to the arguments of configure file ! You can use the matlab format for mesh input and gmv or tecplot format to read the output. Regarding PETSC, check if you have the environment variables $PETSC_ARCH and $PETSC_DIR properly defined. Ahmed On Sat, 2004-03-06 at 21:10, Yuna wrote: > Yes, I use the Unix Sun compiler. When I run make METHOD=dbg, it will > create some files like xdrIO.C, xdr_cxx.C, xdrIO.sparc-sun-solaris2.9.g.o... > in the src/util directory. Do you have any other ways to link the library. > > Others, PETSc is installed in my unix system, how can I make configure to > find it? > > Thanks a lot. > > ----- Original Message ----- > From: "John Peterson" <pet...@cf...> > To: "Yuna" <hyuna@CLEMSON.EDU> > Cc: "Ahmed EL-Sheikh" <els...@mc...>; > <lib...@li...> > Sent: Saturday, March 06, 2004 8:57 PM > Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > > > > Yuna writes: > > > Hi, > > > > > > I try to run example again. I go to the directory /examples, and > > > run "make METHOD=dbg", all of examples can be compied, but no any > > > executable files were created. Look the compile informations: So > > > what does this mean? > > For some reason it's not linking correctly. All the error messages are > > coming from the xdr libraries, which is strange since xdr came from Sun! > > > > -John |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-07 15:56:48
|
Hi Ahmed, Thanks for your advise. I set the environment variables in my .cshrc file, now PETSC directory has been found by the configure. Good! I am now try to run Make again! I still have several things I can's get clearly: 1). What is the different when running make on "OPTIMAL MODE" and "DEBUG MODE"? Which one is better? And generally what method should we use? 2). I remember the input file can be IDEAS .unv file? Am I right? How do I use it? 3). I have a project for finite element analysis for heterogenous material objects. So I have to include material information in both of my element and node classes. Isn't that a good or bad way to modify the origianl libmesh library or can I extend the original mesh and node classes, or do you have any other better way? I am original a fortran programmer, not C++. The reason I hope to switch to C++ is because I like the style of its thingking way, besides I need to link other optimization library which written in C++. So I hope to hear some expert advise of how should I develop my C++ FE application codes? I will report other progress I made later. Thanks for everyone. Yuna ----- Original Message ----- From: "Ahmed Elsheikh" <els...@mc...> To: "Yuna" <hyuna@CLEMSON.EDU> Cc: <lib...@li...> Sent: Saturday, March 06, 2004 11:10 PM Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > Hi, > > As in the source code documentation, XDR is a platform-independent > binary I/O system. You have to check the linker options, but it is > tricky :) > > As a temporary solution till you get a complete answer, add > > --disable-xdr to the arguments of configure file ! > > You can use the matlab format for mesh input and gmv or tecplot format > to read the output. > > Regarding PETSC, check if you have the environment variables $PETSC_ARCH > and $PETSC_DIR properly defined. > > Ahmed > > > On Sat, 2004-03-06 at 21:10, Yuna wrote: > > Yes, I use the Unix Sun compiler. When I run make METHOD=dbg, it will > > create some files like xdrIO.C, xdr_cxx.C, xdrIO.sparc-sun-solaris2.9.g.o... > > in the src/util directory. Do you have any other ways to link the library. > > > > Others, PETSc is installed in my unix system, how can I make configure to > > find it? > > > > Thanks a lot. > > > > ----- Original Message ----- > > From: "John Peterson" <pet...@cf...> > > To: "Yuna" <hyuna@CLEMSON.EDU> > > Cc: "Ahmed EL-Sheikh" <els...@mc...>; > > <lib...@li...> > > Sent: Saturday, March 06, 2004 8:57 PM > > Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > > > > > > > Yuna writes: > > > > Hi, > > > > > > > > I try to run example again. I go to the directory /examples, and > > > > run "make METHOD=dbg", all of examples can be compied, but no any > > > > executable files were created. Look the compile informations: So > > > > what does this mean? > > > For some reason it's not linking correctly. All the error messages are > > > coming from the xdr libraries, which is strange since xdr came from Sun! > > > > > > -John > |
From: Benjamin S. K. <be...@cf...> - 2004-03-07 19:28:57
|
Yuna wrote: >Hi Ahmed, > > Thanks for your advise. > > I set the environment variables in my .cshrc file, now PETSC directory has >been found by the configure. Good! > > I am now try to run Make again! I still have several things I can's get >clearly: > >1). What is the different when running make on "OPTIMAL MODE" and "DEBUG >MODE"? Which one is better? And generally what method should we use? > > OPT mode tells the compiler to generate optimized code, and it also turns off a lot of debugging checks (like making sure you don't divide by zero, etc...). Optimized code is therefore a lot faster, but if you have a problem it will be very hard to track down. DBG mode on the other hand generates much slower code with a lot of extra safety checks in it. This code also contains debugging symbols, so you can track down problems with a debugger. In general I'd say always develop your stuff in debug mode, and when you have it working right and want to run some real problems switch to optimized mode. If you run in to problems you should switch back to debug mode to find it. >2). I remember the input file can be IDEAS .unv file? Am I right? How do I >use it? > > Sure. If you look in example 1, for instance, you will see something like mesh.read("mesh.xda"); All you need to do is call mesh.read("mesh.unv"); When the file extension is .ucd then the appropriate reader will be used. >3). I have a project for finite element analysis for heterogenous material >objects. So I have to include material information in both of my element and >node classes. Isn't that a good or bad way to modify the origianl libmesh >library or can I extend the original mesh and node classes, or do you have >any other better way? I am original a fortran programmer, not C++. The >reason I hope to switch to C++ is because I like the style of its thingking >way, besides I need to link other optimization library which written in C++. >So I hope to hear some expert advise of how should I develop my C++ FE >application codes? > > Probably all you need to do is use the subdomain id provided in the Elem class. You can do elem->set_subdomain_id() = 10; // or whatever... You can then use elem->subdomain_id() to define your material properties. For instance, you could associate ID 10 with copper, 20 with aluminum, or whatever... Then create a function that defines material properties based on these ids. You probably don't want to associate the nodes with materials since they can live on material interfaces and thus don't belong to a specific material. > I will report other progress I made later. > Good. > Thanks for everyone. > >Yuna >----- Original Message ----- >From: "Ahmed Elsheikh" <els...@mc...> >To: "Yuna" <hyuna@CLEMSON.EDU> >Cc: <lib...@li...> >Sent: Saturday, March 06, 2004 11:10 PM >Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > > > > >>Hi, >> >>As in the source code documentation, XDR is a platform-independent >>binary I/O system. You have to check the linker options, but it is >>tricky :) >> >>As a temporary solution till you get a complete answer, add >> >>--disable-xdr to the arguments of configure file ! >> >>You can use the matlab format for mesh input and gmv or tecplot format >>to read the output. >> >>Regarding PETSC, check if you have the environment variables $PETSC_ARCH >>and $PETSC_DIR properly defined. >> >>Ahmed >> >> >>On Sat, 2004-03-06 at 21:10, Yuna wrote: >> >> >>>Yes, I use the Unix Sun compiler. When I run make METHOD=dbg, it will >>>create some files like xdrIO.C, xdr_cxx.C, >>> >>> >xdrIO.sparc-sun-solaris2.9.g.o... > > >>>in the src/util directory. Do you have any other ways to link the >>> >>> >library. > > >>>Others, PETSc is installed in my unix system, how can I make configure >>> >>> >to > > >>>find it? >>> >>>Thanks a lot. >>> >>>----- Original Message ----- >>>From: "John Peterson" <pet...@cf...> >>>To: "Yuna" <hyuna@CLEMSON.EDU> >>>Cc: "Ahmed EL-Sheikh" <els...@mc...>; >>><lib...@li...> >>>Sent: Saturday, March 06, 2004 8:57 PM >>>Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias >>> >>> >>> >>> >>>>Yuna writes: >>>> > Hi, >>>> > >>>> > I try to run example again. I go to the directory /examples, and >>>> > run "make METHOD=dbg", all of examples can be compied, but no any >>>> > executable files were created. Look the compile informations: So >>>> > what does this mean? >>>>For some reason it's not linking correctly. All the error messages >>>> >>>> >are > > >>>>coming from the xdr libraries, which is strange since xdr came from >>>> >>>> >Sun! > > >>>>-John >>>> >>>> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Libmesh-users mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libmesh-users > > |
From: Daniel D. <d.d...@tu...> - 2004-03-07 20:08:36
|
On Sun, 7 Mar 2004, Yuna wrote: > Hi Ahmed, > > Thanks for your advise. > > I set the environment variables in my .cshrc file, now PETSC directory has > been found by the configure. Good! > > I am now try to run Make again! I still have several things I can's get > clearly: > > 1). What is the different when running make on "OPTIMAL MODE" and "DEBUG > MODE"? Which one is better? And generally what method should we use? That's what i suggest: - 95% of your time spending on libmesh/coding, use debug mode, and use small-sized problems that still reflect everything you want to do later. The neat thing with METHOD=dbg, you can use debuggers to trace what happened, and also get some more hints from libmesh itself... - Only when you are perfectly sure that your code is debugged and gives correct answers, use optimized mode. _Very_ seldom it may happen that you get an error when using opt mode (which didn't occur in dbg), but it's generally harder to track down. I also heavily recommend to consult the PETSc documentation. > > 2). I remember the input file can be IDEAS .unv file? Am I right? How do I > use it? Use some common FE preprocessor. the Universal format is, as the name says, pretty universal. ;) libmesh has both .unv input and output, and also offers some mesh -generation and -modification tools. With this you can also play around with .unv-files: create some mesh in libmesh, write to .unv, edit the .unv-file, read back to libmesh, see whether mesh is ok using the gmv viewer, etc... Rather recently, there is also an interface for tetgen-produced files (.node and .ele). Tetgen is freely available (tetgen.berlios.de or so). > > 3). I have a project for finite element analysis for heterogenous material > objects. So I have to include material information in both of my element and > node classes. Isn't that a good or bad way to modify the origianl libmesh > library or can I extend the original mesh and node classes, or do you have With the MeshData class, you already have full support of arbitrary nodal data: You can associate a std::vector<Number> with any node in the mesh, this should be sufficient... Consult the documentation in there, and also the example dwelling on the MeshData class: http://libmesh.sourceforge.net/ex12.php Prior to modifying libmesh, i'd suggest to go and test out this class. I'd say it already offers everything you need. However to be honest, file I/O in .unv format currently only supports nodal data. Coding the I/O of element-associated data is straightforward, but not yet done (no need for it). compare mesh_data_unv_support.C. File I/O in tetgen format currently supports only read method, but for _both_ nodes and elements, i think. -Daniel > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users > |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-07 19:14:59
|
Hi, I just run the "make METHOD=dbg run_examples", and I made the example 1 complied ok. But I got errors for the example2. See the following information: **************************************************************************** ************ make[1]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/examples' make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' *************************************************************** * Running Example ./ex1 *************************************************************** Mesh Information: mesh_dimension()=3 spatial_dimension()=3 n_nodes()=27 n_elem()=1 n_local_elem()=1 n_active_elem()=1 n_subdomains()=1 n_processors()=1 processor_id()=0 --------------------------------------------------------------------------- - | Reference count information | --------------------------------------------------------------------------- - | 4Elem reference count information: | Creations: 7 | Destructions: 7 | 4Node reference count information: | Creations: 27 | Destructions: 27 --------------------------------------------------------------------------- - *************************************************************** * Done Running Example ./ex1 *************************************************************** make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex1' make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex2' Compiling C++ (in debug mode) ex2.C... Linking ex2... collect2: ld terminated with signal 11 [Segmentation Fault] make[2]: *** [ex2] Error 1 make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/examples/ex2' make[1]: *** [run] Error 2 make[1]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/examples' make: *** [run_examples] Error 2 **************************************************************************** **************** So do you please help me look at what wrong with it? In addition, when I go directly into examples and run " make", it always compiles the code and give me some .o files, but don't build and create any execute files. What the reason is? Yuna ----- Original Message ----- From: "Ahmed Elsheikh" <els...@mc...> To: "Yuna" <hyuna@CLEMSON.EDU> Cc: <lib...@li...> Sent: Saturday, March 06, 2004 11:10 PM Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > Hi, > > As in the source code documentation, XDR is a platform-independent > binary I/O system. You have to check the linker options, but it is > tricky :) > > As a temporary solution till you get a complete answer, add > > --disable-xdr to the arguments of configure file ! > > You can use the matlab format for mesh input and gmv or tecplot format > to read the output. > > Regarding PETSC, check if you have the environment variables $PETSC_ARCH > and $PETSC_DIR properly defined. > > Ahmed > > > On Sat, 2004-03-06 at 21:10, Yuna wrote: > > Yes, I use the Unix Sun compiler. When I run make METHOD=dbg, it will > > create some files like xdrIO.C, xdr_cxx.C, xdrIO.sparc-sun-solaris2.9.g.o... > > in the src/util directory. Do you have any other ways to link the library. > > > > Others, PETSc is installed in my unix system, how can I make configure to > > find it? > > > > Thanks a lot. > > > > ----- Original Message ----- > > From: "John Peterson" <pet...@cf...> > > To: "Yuna" <hyuna@CLEMSON.EDU> > > Cc: "Ahmed EL-Sheikh" <els...@mc...>; > > <lib...@li...> > > Sent: Saturday, March 06, 2004 8:57 PM > > Subject: Re: [Libmesh-users] Libmesh0.4.2 compiling problem in Solorias > > > > > > > Yuna writes: > > > > Hi, > > > > > > > > I try to run example again. I go to the directory /examples, and > > > > run "make METHOD=dbg", all of examples can be compied, but no any > > > > executable files were created. Look the compile informations: So > > > > what does this mean? > > > For some reason it's not linking correctly. All the error messages are > > > coming from the xdr libraries, which is strange since xdr came from Sun! > > > > > > -John > |
From: Benjamin S. K. <be...@cf...> - 2004-03-08 00:26:11
|
I have found a Solaris 2.9 machine (thanks Sourceforge!) that should be similar to yours. I was able to get the default ./configure to work... You will need to change two lines in the Make.common file after running configure: change RPATHFLAG = -Wl,-rpath, to RPATHFLAG = -Wl,-R, and LIBS = to LIBS = -lrpcsvc This is due to differences in the Linux and Sun linkers. I have checked these changes in to the CVS repository. If you follow the anonymous CVS access instructions (http://libmesh.sourceforge.net/installation.php) and download what is currently in the CVS repository you should be able to just ./configure and go. It does seem to take a long time to link the libraries, but all the tests seem to run fine. A few notes on the output from configure that you sent me: -------------- - configure is a GNU tool, and as such looks for GNU compilers first. In your case it found gcc-3.3 and is using it to build the library instead of the Sun Forte compiler. This shouldn't be a problem (indeed, I have never built libMesh with the Forte compiler, so this might be good). However, problems *may* arise if PETSc is built with the Forte compiler and libMesh is not. You should be able to figure out which compiler PETSc was built with by looking in the file $PETSC_DIR/bmake/$PETSC_ARCH/variables To specify which compiler you want to use instead of letting configure detect it automatically you have to use environment variables. For instance, under bash or sh this should work: CXX=CC CC=cc F77=f77 ./configure .... (For other shells you might need to export the environment variables before running configure). After you have configured the library you don't need to worry about the compiler, the right one will be specified in the Make.common file. -------------- - As for the MPI stuff: libMesh will use MPI if it is available, although it is not required. If PETSc is found then MPI is definintely available, and the file $PETSC_DIR/bmake/$PETSC_ARCH/packages is queried to find it. This could pose a problem if your PETSc has been provided as binaries and not built from source. In this case I would be interested in hearing about it and improving the configuration. If PETSc is not there, then a number of other tests are conducted to find a valid MPI implementation. First mpi libraries and header files are looked for in /usr/lib & /usr/include (you can specify a directory with --with-mpi=/path/to/mpi). If nothing is found there then we do a final test to see if the compiler supports MPI directly. This is the case with the AIX compilers or the mpiCC provided by MPICH, for example. There was a bug in the Parmetis configuration that tried to build parmetis even if no valid MPI installation was found. I have fixed that in the CVS branch. |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-09 00:35:17
|
Hi, I am working on Sun unix system, and compiler is CC: sun C++ compiler. And Benjamin has helped me fix some problem so I can run configure in my system. But after I try to make the library, it seemed work, but I can't get any library files such as "libmesh.a". Also I cannot run any examples. Please see the following compilinginformation: **************************************************************************** ************** Compiling C++ (in debug mode) src/base/dof_map.C... Compiling C++ (in debug mode) src/base/dof_map_constraints.C... Compiling C++ (in debug mode) src/base/dof_object.C... Compiling C++ (in debug mode) src/base/libmesh.C... "/users/hyuna/myResearch/libmesh-0.4.2/include/base/getpot.h", line 684: Warning: section hides GetPot::section. 1 Warning(s) detected. Compiling C++ (in debug mode) src/base/node.C... Compiling C++ (in debug mode) src/base/reference_counted_object.C... Compiling C++ (in debug mode) src/base/reference_counter.C... Compiling C++ (in debug mode) src/fe/fe.C... Compiling C++ (in debug mode) src/fe/fe_base.C... Compiling C++ (in debug mode) src/fe/fe_boundary.C... Compiling C++ (in debug mode) src/fe/fe_hierarchic.C... Compiling C++ (in debug mode) src/fe/fe_hierarchic_shape_1D.C... Compiling C++ (in debug mode) src/fe/fe_hierarchic_shape_2D.C... Compiling C++ (in debug mode) src/fe/fe_hierarchic_shape_3D.C... Compiling C++ (in debug mode) src/fe/fe_interface.C... Compiling C++ (in debug mode) src/fe/fe_interface_inf_fe.C... Compiling C++ (in debug mode) src/fe/fe_lagrange.C... Compiling C++ (in debug mode) src/fe/fe_lagrange_shape_1D.C... Compiling C++ (in debug mode) src/fe/fe_lagrange_shape_2D.C... Compiling C++ (in debug mode) src/fe/fe_lagrange_shape_3D.C... Compiling C++ (in debug mode) src/fe/fe_map.C... Compiling C++ (in debug mode) src/fe/fe_monomial.C... Compiling C++ (in debug mode) src/fe/fe_monomial_shape_1D.C... Compiling C++ (in debug mode) src/fe/fe_monomial_shape_2D.C... Compiling C++ (in debug mode) src/fe/fe_monomial_shape_3D.C... Compiling C++ (in debug mode) src/fe/fe_szabab.C... Compiling C++ (in debug mode) src/fe/fe_szabab_shape_1D.C... Compiling C++ (in debug mode) src/fe/fe_szabab_shape_2D.C... Compiling C++ (in debug mode) src/fe/fe_szabab_shape_3D.C... Compiling C++ (in debug mode) src/fe/inf_fe.C... Compiling C++ (in debug mode) src/fe/inf_fe_base_radial.C... Compiling C++ (in debug mode) src/fe/inf_fe_boundary.C... Compiling C++ (in debug mode) src/fe/inf_fe_jacobi_20_00_eval.C... Compiling C++ (in debug mode) src/fe/inf_fe_jacobi_30_00_eval.C... Compiling C++ (in debug mode) src/fe/inf_fe_lagrange_eval.C... Compiling C++ (in debug mode) src/fe/inf_fe_legendre_eval.C... Compiling C++ (in debug mode) src/fe/inf_fe_map.C... Compiling C++ (in debug mode) src/fe/inf_fe_map_eval.C... Compiling C++ (in debug mode) src/fe/inf_fe_static.C... Compiling C++ (in debug mode) src/geom/cell.C... Compiling C++ (in debug mode) src/geom/cell_hex.C... Compiling C++ (in debug mode) src/geom/cell_hex20.C... Compiling C++ (in debug mode) src/geom/cell_hex27.C... Compiling C++ (in debug mode) src/geom/cell_hex8.C... Compiling C++ (in debug mode) src/geom/cell_inf.C... Compiling C++ (in debug mode) src/geom/cell_inf_hex.C... Compiling C++ (in debug mode) src/geom/cell_inf_hex16.C... Compiling C++ (in debug mode) src/geom/cell_inf_hex18.C... Compiling C++ (in debug mode) src/geom/cell_inf_hex8.C... Compiling C++ (in debug mode) src/geom/cell_inf_prism.C... Compiling C++ (in debug mode) src/geom/cell_inf_prism12.C... Compiling C++ (in debug mode) src/geom/cell_inf_prism6.C... Compiling C++ (in debug mode) src/geom/cell_prism.C... Compiling C++ (in debug mode) src/geom/cell_prism15.C... Compiling C++ (in debug mode) src/geom/cell_prism18.C... Compiling C++ (in debug mode) src/geom/cell_prism6.C... Compiling C++ (in debug mode) src/geom/cell_pyramid.C... Compiling C++ (in debug mode) src/geom/cell_pyramid5.C... Compiling C++ (in debug mode) src/geom/cell_tet.C... Compiling C++ (in debug mode) src/geom/cell_tet10.C... Compiling C++ (in debug mode) src/geom/cell_tet4.C... Compiling C++ (in debug mode) src/geom/edge.C... Compiling C++ (in debug mode) src/geom/edge_edge2.C... Compiling C++ (in debug mode) src/geom/edge_edge3.C... Compiling C++ (in debug mode) src/geom/edge_inf_edge2.C... Compiling C++ (in debug mode) src/geom/elem.C... Compiling C++ (in debug mode) src/geom/elem_quality.C... Compiling C++ (in debug mode) src/geom/elem_refinement.C... Compiling C++ (in debug mode) src/geom/elem_type.C... Compiling C++ (in debug mode) src/geom/face.C... Compiling C++ (in debug mode) src/geom/face_inf_quad.C... Compiling C++ (in debug mode) src/geom/face_inf_quad4.C... Compiling C++ (in debug mode) src/geom/face_inf_quad6.C... Compiling C++ (in debug mode) src/geom/face_quad.C... Compiling C++ (in debug mode) src/geom/face_quad4.C... Compiling C++ (in debug mode) src/geom/face_quad8.C... Compiling C++ (in debug mode) src/geom/face_quad9.C... Compiling C++ (in debug mode) src/geom/face_tri.C... Compiling C++ (in debug mode) src/geom/face_tri3.C... Compiling C++ (in debug mode) src/geom/face_tri6.C... Compiling C++ (in debug mode) src/geom/plane.C... Compiling C++ (in debug mode) src/geom/point.C... Compiling C++ (in debug mode) src/geom/sphere.C... Compiling C++ (in debug mode) src/geom/surface.C... Compiling C++ (in debug mode) src/mesh/boundary_info.C... Compiling C++ (in debug mode) src/mesh/boundary_mesh.C... Compiling C++ (in debug mode) src/mesh/mesh.C... Compiling C++ (in debug mode) src/mesh/mesh_base.C... Compiling C++ (in debug mode) src/mesh/mesh_base_modification.C... Compiling C++ (in debug mode) src/mesh/mesh_communication.C... Compiling C++ (in debug mode) src/mesh/mesh_data.C... Compiling C++ (in debug mode) src/mesh/mesh_data_tetgen_support.C... Compiling C++ (in debug mode) src/mesh/mesh_data_unv_support.C... Compiling C++ (in debug mode) src/mesh/mesh_data_xdr_support.C... Compiling C++ (in debug mode) src/mesh/mesh_diva_support.C... Compiling C++ (in debug mode) src/mesh/mesh_exodus_support.C... Compiling C++ (in debug mode) src/mesh/mesh_generation.C... Compiling C++ (in debug mode) src/mesh/mesh_misc_support.C... Compiling C++ (in debug mode) src/mesh/mesh_modification.C... Compiling C++ (in debug mode) src/mesh/mesh_refinement.C... Compiling C++ (in debug mode) src/mesh/mesh_refinement_flagging.C... Compiling C++ (in debug mode) src/mesh/mesh_refinement_smoothing.C... Compiling C++ (in debug mode) src/mesh/mesh_smoother.C... Compiling C++ (in debug mode) src/mesh/mesh_smoother_laplace.C... Compiling C++ (in debug mode) src/mesh/mesh_tecplot_support.C... Compiling C++ (in debug mode) src/mesh/mesh_tetgen_support.C... Compiling C++ (in debug mode) src/mesh/mesh_ucd_support.C... Compiling C++ (in debug mode) src/mesh/mesh_unv_support.C... Compiling C++ (in debug mode) src/mesh/mesh_xdr_support.C... Compiling C++ (in debug mode) src/numerics/analytic_function.C... Compiling C++ (in debug mode) src/numerics/coupling_matrix.C... Compiling C++ (in debug mode) src/numerics/dense_matrix.C... Compiling C++ (in debug mode) src/numerics/dense_matrix_base.C... Compiling C++ (in debug mode) src/numerics/dense_submatrix.C... Compiling C++ (in debug mode) src/numerics/dense_subvector.C... Compiling C++ (in debug mode) src/numerics/dense_vector.C... Compiling C++ (in debug mode) src/numerics/dense_vector_base.C... Compiling C++ (in debug mode) src/numerics/distributed_vector.C... Compiling C++ (in debug mode) src/numerics/error_estimator.C... Compiling C++ (in debug mode) src/numerics/function_base.C... Compiling C++ (in debug mode) src/numerics/laspack_interface.C... Compiling C++ (in debug mode) src/numerics/laspack_matrix.C... Compiling C++ (in debug mode) src/numerics/laspack_vector.C... Compiling C++ (in debug mode) src/numerics/linear_solver_interface.C... Compiling C++ (in debug mode) src/numerics/mesh_function.C... Compiling C++ (in debug mode) src/numerics/numeric_vector.C... Compiling C++ (in debug mode) src/numerics/petsc_interface.C... Compiling C++ (in debug mode) src/numerics/petsc_matrix.C... Compiling C++ (in debug mode) src/numerics/petsc_vector.C... Compiling C++ (in debug mode) src/numerics/sparse_matrix.C... Compiling C++ (in debug mode) src/numerics/type_vector.C... Compiling C++ (in debug mode) src/partitioning/centroid_partitioner.C... Compiling C++ (in debug mode) src/partitioning/linear_partitioner.C... Compiling C++ (in debug mode) src/partitioning/metis_partitioner.C... Compiling C++ (in debug mode) src/partitioning/parmetis_partitioner.C... Compiling C++ (in debug mode) src/partitioning/partitioner.C... Compiling C++ (in debug mode) src/partitioning/partitioner_factory.C... Compiling C++ (in debug mode) src/partitioning/sfc_partitioner.C... Compiling C++ (in debug mode) src/quadrature/quadrature.C... Compiling C++ (in debug mode) src/quadrature/quadrature_build.C... Compiling C++ (in debug mode) src/quadrature/quadrature_gauss.C... Compiling C++ (in debug mode) src/quadrature/quadrature_gauss_1D.C... Compiling C++ (in debug mode) src/quadrature/quadrature_gauss_2D.C... "src/quadrature/quadrature_gauss_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_gauss_3D.C... "src/quadrature/quadrature_gauss_3D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_jacobi.C... Compiling C++ (in debug mode) src/quadrature/quadrature_jacobi_1D.C... Compiling C++ (in debug mode) src/quadrature/quadrature_rules.C... Compiling C++ (in debug mode) src/quadrature/quadrature_simpson.C... Compiling C++ (in debug mode) src/quadrature/quadrature_simpson_1D.C... Compiling C++ (in debug mode) src/quadrature/quadrature_simpson_2D.C... "src/quadrature/quadrature_simpson_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_simpson_3D.C... "src/quadrature/quadrature_simpson_3D.C", line 30: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_trap.C... Compiling C++ (in debug mode) src/quadrature/quadrature_trap_1D.C... Compiling C++ (in debug mode) src/quadrature/quadrature_trap_2D.C... "src/quadrature/quadrature_trap_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_trap_3D.C... "src/quadrature/quadrature_trap_3D.C", line 30: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/solvers/equation_systems.C... Compiling C++ (in debug mode) src/solvers/equation_systems_io.C... Compiling C++ (in debug mode) src/solvers/explicit_system.C... Compiling C++ (in debug mode) src/solvers/frequency_system.C... Compiling C++ (in debug mode) src/solvers/implicit_system.C... Compiling C++ (in debug mode) src/solvers/newmark_system.C... "src/solvers/newmark_system.C", line 201: Warning: rhs hides ImplicitSystem::rhs. 1 Warning(s) detected. Compiling C++ (in debug mode) src/solvers/steady_system.C... Compiling C++ (in debug mode) src/solvers/system.C... Compiling C++ (in debug mode) src/solvers/system_io.C... Compiling C++ (in debug mode) src/solvers/system_projection.C... Compiling C++ (in debug mode) src/solvers/transient_system.C... Compiling C++ (in debug mode) src/utils/data_map.C... Compiling C++ (in debug mode) src/utils/error_vector.C... Compiling C++ (in debug mode) src/utils/o_f_stream.C... Compiling C++ (in debug mode) src/utils/perf_log.C... Compiling C++ (in debug mode) src/utils/point_locator_base.C... Compiling C++ (in debug mode) src/utils/point_locator_list.C... Compiling C++ (in debug mode) src/utils/point_locator_tree.C... Compiling C++ (in debug mode) src/utils/statistics.C... Compiling C++ (in debug mode) src/utils/tree.C... Compiling C++ (in debug mode) src/utils/tree_base.C... Compiling C++ (in debug mode) src/utils/tree_node.C... Compiling C++ (in debug mode) src/utils/utility.C... Compiling C++ (in debug mode) src/utils/xdrIO.C... Compiling C++ (in debug mode) src/utils/xdr_cxx.C... Linking /users/hyuna/myResearch/libmesh-0.4.2/lib/sparc-sun-solaris2.8_dbg/libmesh.s o make[1]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib' ---------------------------------------------- ------- Building Contributed Packages -------- ---------------------------------------------- --- Building LASPACK ------------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/laspack' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/laspack' --- Building Metis --------------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/metis/Lib' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/metis/Lib' --- Building Parmetis ------------------------ make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/parmetis/Lib' --- Building sfcurves ------------------------ make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/sfcurves' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/sfcurves' --- Building libgzstream --------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/gzstream' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib/gzstream' ---------------------------------------------- ----- Done Building Contributed Packages ----- ---------------------------------------------- make[1]: Leaving directory `/users/hyuna/myResearch/libmesh-0.4.2/contrib' **************************************************************************** *********** I just get file like "libmesh.so", So does anyone ever have this problem and give me some hints? Thanks a lot. Yuna |
From: John P. <pet...@cf...> - 2004-03-09 04:40:21
|
Yuna writes: > Hi, > > I just get file like "libmesh.so", So does anyone ever have this problem > and give me some hints? libmesh.so is a shared object file. You should be able to use it in the same way as the libmesh.a file. The .so is the default library to build unless you use --disable-shared. -John |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-09 15:03:13
|
Morning Benjamin, I can now bulid library. I found there are some warnings. I wrote them here for your reference: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Compiling C++ (in debug mode) src/base/dof_map.C... ..... Compiling C++ (in debug mode) src/base/libmesh.C... "/users/hyuna/myResearch/libmesh/include/base/getpot.h", line 684: Warning: section hides GetPot::section. 1 Warning(s) detected. Compiling C++ (in debug mode) src/base/node.C... ............................... Compiling C++ (in debug mode) src/fe/fe_xyz.C... "src/fe/fe_xyz.C", line 212: Warning: xyz hides FEBase::xyz. "src/fe/fe_xyz.C", line 212: Warning: xyz hides FEBase::xyz. "src/fe/fe_xyz.C", line 212: Warning: xyz hides FEBase::xyz. 3 Warning(s) detected. Compiling C++ (in debug mode) src/fe/fe_xyz_shape_1D.C... ...................................... Compiling C++ (in debug mode) src/quadrature/quadrature_gauss_2D.C... "src/quadrature/quadrature_gauss_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_gauss_3D.C... "src/quadrature/quadrature_gauss_3D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_jacobi.C... ..... Compiling C++ (in debug mode) src/quadrature/quadrature_simpson_2D.C... "src/quadrature/quadrature_simpson_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_simpson_3D.C... "src/quadrature/quadrature_simpson_3D.C", line 30: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_trap.C... ................. Compiling C++ (in debug mode) src/quadrature/quadrature_trap_2D.C... "src/quadrature/quadrature_trap_2D.C", line 28: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/quadrature/quadrature_trap_3D.C... "src/quadrature/quadrature_trap_3D.C", line 30: Warning: _type hides QBase::_type. 1 Warning(s) detected. Compiling C++ (in debug mode) src/solvers/equation_systems.C... ....... Compiling C++ (in debug mode) src/solvers/newmark_system.C... "src/solvers/newmark_system.C", line 201: Warning: rhs hides ExplicitSystem::rhs. 1 Warning(s) detected. Compiling C++ (in debug mode) src/solvers/steady_system.C... ....................... Linking /users/hyuna/myResearch/libmesh/lib/sparc-sun-solaris2.8_dbg/libmesh.so make[1]: Entering directory `/users/hyuna/myResearch/libmesh/contrib' ---------------------------------------------- ------- Building Contributed Packages -------- ---------------------------------------------- --- Building LASPACK ------------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh/contrib/laspack' Compiling C (in debug mode) eigenval.c.. .... Compiling C (in debug mode) rtc.c... Linking ../lib/sparc-sun-solaris2.8_dbg/liblaspack.so make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib/laspack' --- Building Metis --------------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh/contrib/metis/Lib' Compiling C (in debug mode) balance.c... ........ Compiling C (in debug mode) checkgraph.c... "checkgraph.c", line 124: warning: implicit function declaration: __GKfree Compiling C (in debug mode) coarsen.c... Compiling C (in debug mode) compress.c... "compress.c", line 151: warning: implicit function declaration: __GKfree Compiling C (in debug mode) debug.c... Compiling C (in debug mode) estmem.c... "estmem.c", line 102: warning: implicit function declaration: __GKfree Compiling C (in debug mode) fm.c... Compiling C (in debug mode) fortran.c... Compiling C (in debug mode) frename.c... Compiling C (in debug mode) graph.c... "graph.c", line 445: warning: implicit function declaration: __GKfree Compiling C (in debug mode) initpart.c... "initpart.c", line 202: warning: implicit function declaration: __GKfree Compiling C (in debug mode) kmetis.c... "kmetis.c", line 124: warning: implicit function declaration: __GKfree Compiling C (in debug mode) kvmetis.c... "kvmetis.c", line 125: warning: implicit function declaration: __GKfree Compiling C (in debug mode) kwayfm.c... Compiling C (in debug mode) kwayrefine.c... "kwayrefine.c", line 74: warning: implicit function declaration: __GKfree Compiling C (in debug mode) kwayvolfm.c... "kwayvolfm.c", line 151: warning: implicit function declaration: __GKfree Compiling C (in debug mode) kwayvolrefine.c... "kwayvolrefine.c", line 76: warning: implicit function declaration: __GKfree Compiling C (in debug mode) match.c... Compiling C (in debug mode) mbalance.c... Compiling C (in debug mode) mbalance2.c... Compiling C (in debug mode) mcoarsen.c... Compiling C (in debug mode) memory.c... "memory.c", line 89: warning: implicit function declaration: __GKfree Compiling C (in debug mode) mesh.c... Compiling C (in debug mode) meshpart.c... "meshpart.c", line 101: warning: implicit function declaration: __GKfree Compiling C (in debug mode) mfm.c... Compiling C (in debug mode) mfm2.c... Compiling C (in debug mode) mincover.c... "mincover.c", line 118: warning: implicit function declaration: __GKfree Compiling C (in debug mode) minitpart.c... "minitpart.c", line 98: warning: implicit function declaration: __GKfree "minitpart.c", line 251: warning: implicit function declaration: SelectQueueOneWay Compiling C (in debug mode) minitpart2.c... "minitpart2.c", line 95: warning: implicit function declaration: __GKfree Compiling C (in debug mode) mkmetis.c... "mkmetis.c", line 119: warning: implicit function declaration: __GKfree Compiling C (in debug mode) mkwayfmh.c... Compiling C (in debug mode) mkwayrefine.c... Compiling C (in debug mode) mmatch.c... Compiling C (in debug mode) mmd.c... Compiling C (in debug mode) mpmetis.c... "mpmetis.c", line 125: warning: implicit function declaration: __GKfree Compiling C (in debug mode) mrefine.c... Compiling C (in debug mode) mrefine2.c... Compiling C (in debug mode) mutil.c... Compiling C (in debug mode) myqsort.c... Compiling C (in debug mode) ometis.c... "ometis.c", line 138: warning: implicit function declaration: __GKfree Compiling C (in debug mode) parmetis.c... "parmetis.c", line 143: warning: implicit function declaration: __GKfree Compiling C (in debug mode) pmetis.c... "pmetis.c", line 138: warning: implicit function declaration: __GKfree Compiling C (in debug mode) pqueue.c... "pqueue.c", line 110: warning: implicit function declaration: __GKfree Compiling C (in debug mode) refine.c... Compiling C (in debug mode) separator.c... "separator.c", line 40: warning: implicit function declaration: __GKfree Compiling C (in debug mode) sfm.c... Compiling C (in debug mode) srefine.c... Compiling C (in debug mode) stat.c... "stat.c", line 123: warning: implicit function declaration: __GKfree Compiling C (in debug mode) subdomains.c... "subdomains.c", line 885: warning: implicit function declaration: __GKfree Compiling C (in debug mode) timing.c... Compiling C (in debug mode) util.c... Linking ../../lib/sparc-sun-solaris2.8_dbg/libmetis.so make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib/metis/Lib' --- Building Parmetis ------------------------ make[2]: Entering directory `/users/hyuna/myResearch/libmesh/contrib/parmetis/Lib' Compiling C (in debug mode) akwayfm.c... "akwayfm.c", line 621: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) ametis.c... "ametis.c", line 158: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) backcompat.c... Compiling C (in debug mode) balancemylink.c... "balancemylink.c", line 339: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) coarsen.c... "coarsen.c", line 481: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) comm.c... Compiling C (in debug mode) csrmatch.c... "csrmatch.c", line 86: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) debug.c... Compiling C (in debug mode) diffutil.c... "diffutil.c", line 125: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) fpqueue.c... Compiling C (in debug mode) frename.c... Compiling C (in debug mode) gkmetis.c... "gkmetis.c", line 75: warning: implicit function declaration: METIS_WPartGraphKway "gkmetis.c", line 250: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) grsetup.c... "grsetup.c", line 273: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) iidxsort.c... Compiling C (in debug mode) iintsort.c... Compiling C (in debug mode) ikeysort.c... Compiling C (in debug mode) ikeyvalsort.c... Compiling C (in debug mode) initbalance.c... "initbalance.c", line 91: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) initmsection.c... "initmsection.c", line 139: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) initpart.c... "initpart.c", line 191: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) kmetis.c... "kmetis.c", line 71: warning: implicit function declaration: METIS_WPartGraphKway "kmetis.c", line 166: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) kwaybalance.c... "kwaybalance.c", line 449: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) kwayfm.c... "kwayfm.c", line 591: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) kwayrefine.c... Compiling C (in debug mode) lmatch.c... "lmatch.c", line 122: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) match.c... "match.c", line 308: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) mdiffusion.c... "mdiffusion.c", line 248: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) memory.c... "memory.c", line 50: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) mesh.c... "mesh.c", line 327: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) mmetis.c... "mmetis.c", line 90: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) move.c... Compiling C (in debug mode) node_refine.c... "node_refine.c", line 355: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) ometis.c... Compiling C (in debug mode) order.c... "order.c", line 93: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) pspases.c... "pspases.c", line 98: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) redomylink.c... "redomylink.c", line 172: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) remap.c... "remap.c", line 159: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) rmetis.c... "rmetis.c", line 152: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) selectq.c... Compiling C (in debug mode) serial.c... "serial.c", line 223: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) setup.c... Compiling C (in debug mode) stat.c... "stat.c", line 52: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) timer.c... Compiling C (in debug mode) util.c... Compiling C (in debug mode) wave.c... "wave.c", line 237: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) weird.c... "weird.c", line 95: warning: implicit function declaration: GKfree__ Compiling C (in debug mode) xyzpart.c... "xyzpart.c", line 252: warning: implicit function declaration: GKfree__ Linking ../../lib/sparc-sun-solaris2.8_dbg/libparmetis.so make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib/parmetis/Lib' --- Building sfcurves ------------------------ make[2]: Entering directory `/users/hyuna/myResearch/libmesh/contrib/sfcurves' Compiling C (in debug mode) cmp.c... Compiling C (in debug mode) hilbert.c... Compiling C (in debug mode) morton.c... Linking ../lib/sparc-sun-solaris2.8_dbg/libsfcurves.so make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib/sfcurves' --- Building libgzstream --------------------- make[2]: Entering directory `/users/hyuna/myResearch/libmesh/contrib/gzstream' Compiling C++ (in debug mode) gzstream.C... Linking ../lib/sparc-sun-solaris2.8_dbg/libgzstream.so make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib/gzstream' ---------------------------------------------- ----- Done Building Contributed Packages ----- ---------------------------------------------- make[1]: Leaving directory `/users/hyuna/myResearch/libmesh/contrib' Best yuna |
From: Yuna <hyuna@CLEMSON.EDU> - 2004-03-09 15:07:48
|
Hi Benjamin, I have built the library, but I have some problems when I built examples. The error looks like: **************************************************************************** ** make[1]: Entering directory `/users/hyuna/myResearch/libmesh/examples' make[2]: Entering directory `/users/hyuna/myResearch/libmesh/examples/ex1' Compiling C++ (in debug mode) ex1.C... Linking ex1... Undefined first referenced symbol in file void PetscVector<double>::add_vector(const NumericVector<double>&,SparseMatrix<double>&) /users/hyuna/myResearch/libmesh/lib/sparc-sun-solaris2.8_dbg/libmesh.so ld: fatal: Symbol referencing errors. No output written to ex1 make[2]: *** [ex1] Error 1 make[2]: Leaving directory `/users/hyuna/myResearch/libmesh/examples/ex1' make[1]: *** [run] Error 2 make[1]: Leaving directory `/users/hyuna/myResearch/libmesh/examples' make: *** [run_examples] Error 2 **************************************************************************** **** Could you help me fix it? Thanks a lot. Yuna ----- Original Message ----- From: "John Peterson" <pet...@cf...> To: "Yuna" <hyuna@CLEMSON.EDU> Cc: "Benjamin S. Kirk" <be...@cf...>; <lib...@li...> Sent: Monday, March 08, 2004 11:23 PM Subject: [Libmesh-users] Call for any support for Strange Linking problem > Yuna writes: > > Hi, > > > > > I just get file like "libmesh.so", So does anyone ever have this problem > > and give me some hints? > libmesh.so is a shared object file. You should be able to use it in the same > way as the libmesh.a file. The .so is the default library to build unless you > use --disable-shared. > > -John |