Menu
▾
▴
libmesh-users — General information for libmesh users
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
(27) |
Dec
(31) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(6) |
Feb
(15) |
Mar
(33) |
Apr
(10) |
May
(46) |
Jun
(11) |
Jul
(21) |
Aug
(15) |
Sep
(13) |
Oct
(23) |
Nov
(1) |
Dec
(8) |
| 2005 |
Jan
(27) |
Feb
(57) |
Mar
(86) |
Apr
(23) |
May
(37) |
Jun
(34) |
Jul
(24) |
Aug
(17) |
Sep
(50) |
Oct
(24) |
Nov
(10) |
Dec
(60) |
| 2006 |
Jan
(47) |
Feb
(46) |
Mar
(127) |
Apr
(19) |
May
(26) |
Jun
(62) |
Jul
(47) |
Aug
(51) |
Sep
(61) |
Oct
(42) |
Nov
(50) |
Dec
(33) |
| 2007 |
Jan
(60) |
Feb
(55) |
Mar
(77) |
Apr
(102) |
May
(82) |
Jun
(102) |
Jul
(169) |
Aug
(117) |
Sep
(80) |
Oct
(37) |
Nov
(51) |
Dec
(43) |
| 2008 |
Jan
(71) |
Feb
(94) |
Mar
(98) |
Apr
(125) |
May
(54) |
Jun
(119) |
Jul
(60) |
Aug
(111) |
Sep
(118) |
Oct
(125) |
Nov
(119) |
Dec
(94) |
| 2009 |
Jan
(109) |
Feb
(38) |
Mar
(93) |
Apr
(88) |
May
(29) |
Jun
(57) |
Jul
(53) |
Aug
(48) |
Sep
(68) |
Oct
(151) |
Nov
(23) |
Dec
(35) |
| 2010 |
Jan
(84) |
Feb
(60) |
Mar
(184) |
Apr
(112) |
May
(60) |
Jun
(90) |
Jul
(23) |
Aug
(70) |
Sep
(119) |
Oct
(27) |
Nov
(47) |
Dec
(54) |
| 2011 |
Jan
(22) |
Feb
(19) |
Mar
(92) |
Apr
(93) |
May
(35) |
Jun
(91) |
Jul
(32) |
Aug
(61) |
Sep
(7) |
Oct
(69) |
Nov
(81) |
Dec
(23) |
| 2012 |
Jan
(64) |
Feb
(95) |
Mar
(35) |
Apr
(36) |
May
(63) |
Jun
(98) |
Jul
(70) |
Aug
(171) |
Sep
(149) |
Oct
(64) |
Nov
(67) |
Dec
(126) |
| 2013 |
Jan
(108) |
Feb
(104) |
Mar
(171) |
Apr
(133) |
May
(108) |
Jun
(100) |
Jul
(93) |
Aug
(126) |
Sep
(74) |
Oct
(59) |
Nov
(145) |
Dec
(93) |
| 2014 |
Jan
(38) |
Feb
(45) |
Mar
(26) |
Apr
(41) |
May
(125) |
Jun
(70) |
Jul
(61) |
Aug
(66) |
Sep
(60) |
Oct
(110) |
Nov
(27) |
Dec
(30) |
| 2015 |
Jan
(43) |
Feb
(67) |
Mar
(71) |
Apr
(92) |
May
(39) |
Jun
(15) |
Jul
(46) |
Aug
(63) |
Sep
(84) |
Oct
(82) |
Nov
(69) |
Dec
(45) |
| 2016 |
Jan
(92) |
Feb
(91) |
Mar
(148) |
Apr
(43) |
May
(58) |
Jun
(117) |
Jul
(92) |
Aug
(140) |
Sep
(49) |
Oct
(33) |
Nov
(85) |
Dec
(40) |
| 2017 |
Jan
(41) |
Feb
(36) |
Mar
(49) |
Apr
(41) |
May
(73) |
Jun
(51) |
Jul
(12) |
Aug
(69) |
Sep
(26) |
Oct
(43) |
Nov
(75) |
Dec
(23) |
| 2018 |
Jan
(86) |
Feb
(36) |
Mar
(50) |
Apr
(28) |
May
(53) |
Jun
(65) |
Jul
(26) |
Aug
(43) |
Sep
(32) |
Oct
(28) |
Nov
(52) |
Dec
(17) |
| 2019 |
Jan
(39) |
Feb
(26) |
Mar
(71) |
Apr
(30) |
May
(73) |
Jun
(18) |
Jul
(5) |
Aug
(10) |
Sep
(8) |
Oct
(24) |
Nov
(12) |
Dec
(34) |
| 2020 |
Jan
(17) |
Feb
(10) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(3) |
Jul
(8) |
Aug
(15) |
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(4) |
| 2021 |
Jan
(4) |
Feb
(4) |
Mar
(21) |
Apr
(14) |
May
(13) |
Jun
(18) |
Jul
(1) |
Aug
(39) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(2) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2023 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
|
From: Yuna <hy...@CL...> - 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: Yuna <hy...@CL...> - 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: John P. <pet...@cf...> - 2004-03-06 22:51:16
|
Yuna writes: > Hi all, > > Does somebody ever link 0.4.2 on Sun Solaris gcc or Linux g++ successfuly? I haven't spoken with anyone personally. I would be interested to see if you can get it working. None of the devs has access to a solaris box. (Ben?) > First, I run ./configure------------It runs ok except telling > me:"checking for /include/petsc.h... no; note: MPI library path > not given... trying prefix=/usr; g++ Compiler Does NOT Support > MPI..." How do I deal with this? Had I download PERSC? I don't > use parallel at this time? You should be able to build/compile parts of the library even without MPI. Does your machine have MPI, but we are just not finding it correctly? Please comment. > Second, I run the Makefile by typing "make", it runs ok till > contrib/parmetis. I guess it is the mpi stuff problem? How do I > solve it? Also I can't make any of the example run, why? Where can > I find the detailed information for the instllation of libfem? I think we may have a slight configure bug in which Parmetis tries to compile even if MPI is not available. Parmetis will never compile without MPI. If I can find the bug I will fix it. -John |
|
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 <hy...@CL...> - 2004-03-06 21:26:12
|
Hi all, Does somebody ever link 0.4.2 on Sun Solaris gcc or Linux g++ = successfuly? First, I run ./configure------------It runs ok except telling = me:"checking for /include/petsc.h... no; note: MPI library path not = given... trying prefix=3D/usr; g++ Compiler Does NOT Support MPI..." = How do I deal with this? Had I download PERSC? I don't use parallel at = this time? --------------------------------------------- ----------- Configuring libMesh ------------- --------------------------------------------- checking build system type... sparc-sun-solaris2.8 checking host system type... sparc-sun-solaris2.8 checking target system type... sparc-sun-solaris2.8 checking for g++... g++ checking for C++ compiler default output... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables...=20 checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed <<< C++ compiler is gcc-3.3 >>> checking how to run the C++ preprocessor... g++ -E checking for egrep... egrep checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... no checking for unistd.h... yes checking for short int... yes checking size of short int... 2 checking for int... yes checking size of int... 4 checking for long int... yes checking size of long int... 4 checking for float... yes checking size of float... 4 checking for double... yes checking size of double... 8 checking for void *... yes checking size of void *... 4 checking getopt.h usability... no checking getopt.h presence... no checking for getopt.h... no checking whether the compiler implements namespaces... yes checking whether the compiler has locale... yes checking whether the compiler has stringstream... yes checking hash_map usability... no checking hash_map presence... no checking for hash_map... no checking ext/hash_map usability... yes checking ext/hash_map presence... yes checking for ext/hash_map... yes checking hash_set usability... no checking hash_set presence... no checking for hash_set... no checking ext/hash_set usability... yes checking ext/hash_set presence... yes checking for ext/hash_set... yes <<< Configuring library with AMR support >>> <<< Configuring library with expensive data structures enabled >>> checking rpc/rpc.h usability... yes checking rpc/rpc.h presence... yes checking for rpc/rpc.h... yes <<< Configuring library with XDR support >>> <<< Configuring library with real number support >>> <<< Configuring library with reference counting support >>> checking for ./contrib/netcdf/lib/sparc-sun-solaris2.8/libnetcdf.a... no checking for ./contrib/netcdf/include/netcdf.h... no --------------------------------------------- ----- Configuring for optional packages ----- --------------------------------------------- checking for /include/petsc.h... no note: MPI library path not given... trying prefix=3D/usr g++ Compiler Does NOT Support MPI... checking for ./contrib/laspack/lastypes.h... yes <<< Configuring library with LASPACK version 1.12.3 support >>> checking for ./contrib/sfcurves/sfcurves.h... yes <<< Configuring library with SFC support >>> checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for gzopen in -lz... yes checking for ./contrib/gzstream/gzstream.h... yes <<< Configuring library with gzstreams support >>> checking for ./contrib/tecplot/lib/sparc-sun-solaris2.8/tecio.a... no checking for ./contrib/tecplot/include/TECIO.h... yes checking for ./contrib/metis/Lib/metis.h... yes <<< Configuring library with Metis support >>> checking for doxygen... /usr/local/bin/doxygen checking for dot... no ---------------------------------------------- --- Done configuring for optional packages --- ---------------------------------------------- checking for perl... /bin/perl configure: creating ./config.status config.status: creating Make.common config.status: creating doc/Doxyfile config.status: creating contrib/bin/libmesh-config config.status: creating include/base/libmesh_config.h --------------------------------------------- --------- Done Configuring libMesh ---------- --------------------------------------------- Second, I run the Makefile by typing "make", it runs ok till = contrib/parmetis. I guess it is the mpi stuff problem? How do I solve = it? Also I can't make any of the example run, why? Where can I find the = detailed information for the instllation of libfem? Thanks a lot. Yuna |
|
From: Yuna <hy...@CL...> - 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: KIRK, B. (JSC-E. (NASA) <ben...@na...> - 2004-03-04 14:11:34
|
That means a face neighbor was not found in a case where a valid face
neighbor should exist. The most likely cause of this problem is that in
the refinement process at some point a new node was created where a node
already existed. Clearly, that shouldn't happen... It effectively
introduces a slit in the domain because you have two elements that *should*
share an edge, but they don't.
I'll try and reproduce the error and find out exactly why it happened & what
can be done about it.
-Ben
-----Original Message-----
From: lib...@li...
[mailto:lib...@li...] On Behalf Of Ahmed
EL-Sheikh
Sent: Thursday, March 04, 2004 12:41 AM
To: lib...@li...
Cc: Ahmed El-Sheikh
Subject: [Libmesh-users] I'm confused...
Hi,
As I am playing around with libmesh, I tried to run ex10 but with a
different mesh the mesh was specified as a matlab output file with this
information
4 2
0.000000 0.000000
2.000000 0.000000
2.000000 2.000000
0.000000 2.000000
1 2 3 1
1 3 4 1
Then I did two changes in ex10.C
1- mesh_refinement.uniformly_refine (2);
I chosen not to start with a coarse mesh to see what the error estimator
will do.
2- mesh_refinement.flag_elements_by_error_fraction (error,
0.95, // This is increased from 0.7
0.07,
5);
The I got the a run time error ....
Solving time step 26, time=0.6750...
Refining the mesh...
I'm confused...
[0] src/mesh/mesh_base.C, line 528, compiled Mar 3 2004 at 21:54:19
make: *** [run] Aborted
So what is the problem with this check !!
Thanks in advance.
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
**************************************************
-------------------------------------------------------
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: Ahmed EL-S. <els...@mc...> - 2004-03-04 05:52:23
|
Hi,
As I am playing around with libmesh, I tried to run ex10 but with a
different
mesh the mesh was specified as a matlab output file with this
information
4 2
0.000000 0.000000
2.000000 0.000000
2.000000 2.000000
0.000000 2.000000
1 2 3 1
1 3 4 1
Then I did two changes in ex10.C
1- mesh_refinement.uniformly_refine (2);
I chosen not to start with a coarse mesh to see what the error
estimator will do.
2- mesh_refinement.flag_elements_by_error_fraction (error,
0.95, // This is increased from 0.7
0.07,
5);
The I got the a run time error ....
Solving time step 26, time=0.6750...
Refining the mesh...
I'm confused...
[0] src/mesh/mesh_base.C, line 528, compiled Mar 3 2004 at 21:54:19
make: *** [run] Aborted
So what is the problem with this check !!
Thanks in advance.
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
**************************************************
|
|
From: KIRK, B. (JSC-E. (NASA) <ben...@na...> - 2004-02-24 14:34:47
|
The problem seems to be that gcc 3.0 puts the hash map in the std namespace,
while all the other 3.x releases put it in __gnu_cxx. Since 3.1 came out so
soon after 3.0 I never ran in to this bug. Thanks!
in the file include/mesh/mesh_refinement.h, starting at line 328, change it
to:
#if defined(HAVE_HASH_MAP)
typedef std::hash_multimap<unsigned int, Node*> map_type;
#elif defined(HAVE_EXT_HASH_MAP)
# if __GNUC__ >= 3
# if __GNUC_MINOR__ == 0
typedef std::hash_multimap<unsigned int, Node*> map_type;
# else
typedef __gnu_cxx::hash_multimap<unsigned int, Node*> map_type;
# endif
# else
DIE A HORRIBLE DEATH
# endif
#else
typedef std::multimap<unsigned int, Node*> map_type;
#endif
similarly, in src/mesh/mesh_base.C, starting at line 400, change it to:
#if defined(HAVE_HASH_MAP)
typedef std::hash_multimap<key_type, val_type> map_type;
#elif defined(HAVE_EXT_HASH_MAP)
# if __GNUC__ >= 3
# if __GNUC_MINOR__ == 0
typedef std::hash_multimap<key_type, val_type> map_type;
# else
typedef __gnu_cxx::hash_multimap<key_type, val_type> map_type;
# endif
# else
DIE A HORRIBLE DEATH
# endif
#else
typedef std::multimap<key_type, val_type> map_type;
#endif
Please let me know if this works for you (I don't have access to gcc-3.0
right now). If it does I'll submit the change to CVS so we don't have this
problem in the future.
Thanks!
-Ben
-----Original Message-----
From: lib...@li...
[mailto:lib...@li...] On Behalf Of Rob van Tol
Sent: Tuesday, February 24, 2004 7:17 AM
To: lib...@li...
Subject: [Libmesh-users] (no subject)
Dear libmesh users,
I just downloaded the code and I am trying to compile it. I am using Redhat
7 and a GCC-3.0 compiler.
I get an error message:
ISO C++ forbids declaration of `hash_multimap' with no type.
Can anyone tell me how to solve this ??
I have included the configure and make messages below.
Thank you in advance,
Kind regards,
ROB
configuring libMesh -------------
---------------------------------------------
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
<<< C++ compiler is gcc-3.0 >>>
checking how to run the C++ preprocessor... g++ -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for short int... yes
checking size of short int... 2
checking for int... yes
checking size of int... 4
checking for long int... yes
checking size of long int... 4
checking for float... yes
checking size of float... 4
checking for double... yes
checking size of double... 8
checking for void *... yes
checking size of void *... 4
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking whether the compiler implements namespaces... yes
checking whether the compiler has locale... yes
checking whether the compiler has stringstream... yes
checking hash_map usability... no
checking hash_map presence... no
checking for hash_map... no
checking ext/hash_map usability... yes
checking ext/hash_map presence... yes
checking for ext/hash_map... yes
checking hash_set usability... no
checking hash_set presence... no
checking for hash_set... no
checking ext/hash_set usability... yes
checking ext/hash_set presence... yes
checking for ext/hash_set... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
<<< Configuring library with AMR support >>>
<<< Configuring library with expensive data structures enabled >>>
checking rpc/rpc.h usability... yes
checking rpc/rpc.h presence... yes
checking for rpc/rpc.h... yes
<<< Configuring library with XDR support >>>
<<< Configuring library with real number support >>>
<<< Configuring library with reference counting support >>>
checking for ./contrib/netcdf/lib/i686-pc-linux-gnu/libnetcdf.a... no
checking for ./contrib/netcdf/include/netcdf.h... no
---------------------------------------------
----- Configuring for optional packages -----
---------------------------------------------
checking for ./contrib/sfcurves/sfcurves.h... yes
<<< Configuring library with SFC support >>>
checking for ./contrib/gzstream/gzstream.h... yes
<<< Configuring library with gzstreams support >>>
checking for ./contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a... yes
checking for ./contrib/tecplot/include/TECIO.h... yes
<<< Configuring library with Tecplot API support >>>
checking for ./contrib/laspack/lastypes.h... yes
<<< Configuring library with LASPACK version 1.12.3 support >>>
checking for /include/petsc.h... no
checking for /include/mpi.h... no
checking for /lib/libmpich.a... no
checking for ./contrib/metis/Lib/metis.h... yes
<<< Configuring library with Metis support >>>
checking for doxygen... /usr/bin/doxygen
checking for dot... no
----------------------------------------------
--- Done configuring for optional packages ---
----------------------------------------------
checking for perl... /usr/bin/perl
configure: creating ./config.status
config.status: creating Make.common
config.status: creating include/base/libmesh_config.h
configure: creating ./config.status
config.status: creating Make.common
config.status: creating doc/Doxyfile
config.status: creating include/base/libmesh_config.h
config.status: include/base/libmesh_config.h is unchanged
---------------------------------------------
--------- Done Configuring libMesh ----------
---------------------------------------------
[vlr@pc02011 libmesh-0.4.1]$ make
Compiling C++ (in optimized mode) src/base/dof_map.C...
Compiling C++ (in optimized mode) src/base/dof_map_constraints.C...
Compiling C++ (in optimized mode) src/base/dof_object.C...
Compiling C++ (in optimized mode) src/base/equation_systems.C...
Compiling C++ (in optimized mode) src/base/equation_systems_io.C...
Compiling C++ (in optimized mode) src/base/frequency_system.C...
Compiling C++ (in optimized mode) src/base/libmesh.C...
Compiling C++ (in optimized mode) src/base/newmark_system.C...
Compiling C++ (in optimized mode) src/base/node.C...
Compiling C++ (in optimized mode) src/base/reference_counted_object.C...
Compiling C++ (in optimized mode) src/base/reference_counter.C...
Compiling C++ (in optimized mode) src/base/steady_system.C...
Compiling C++ (in optimized mode) src/base/system_base.C...
Compiling C++ (in optimized mode) src/base/system_base_io.C...
Compiling C++ (in optimized mode) src/base/system_base_projection.C...
Compiling C++ (in optimized mode) src/base/transient_system.C...
Compiling C++ (in optimized mode) src/fe/fe_base.C...
Compiling C++ (in optimized mode) src/fe/fe_boundary.C...
Compiling C++ (in optimized mode) src/fe/fe.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/fe_interface.C...
Compiling C++ (in optimized mode) src/fe/fe_interface_inf_fe.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/fe_map.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_base_radial.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_boundary.C...
Compiling C++ (in optimized mode) src/fe/inf_fe.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_jacobi_20_00_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_jacobi_30_00_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_lagrange_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_legendre_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_map.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_map_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_static.C...
Compiling C++ (in optimized mode) src/geom/cell.C...
Compiling C++ (in optimized mode) src/geom/cell_hex20.C...
Compiling C++ (in optimized mode) src/geom/cell_hex27.C...
Compiling C++ (in optimized mode) src/geom/cell_hex8.C...
Compiling C++ (in optimized mode) src/geom/cell_hex.C...
Compiling C++ (in optimized mode) src/geom/cell_inf.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex16.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex18.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex8.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism12.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism6.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism.C...
Compiling C++ (in optimized mode) src/geom/cell_prism15.C...
Compiling C++ (in optimized mode) src/geom/cell_prism18.C...
Compiling C++ (in optimized mode) src/geom/cell_prism6.C...
Compiling C++ (in optimized mode) src/geom/cell_prism.C...
Compiling C++ (in optimized mode) src/geom/cell_pyramid5.C...
Compiling C++ (in optimized mode) src/geom/cell_pyramid.C...
Compiling C++ (in optimized mode) src/geom/cell_tet10.C...
Compiling C++ (in optimized mode) src/geom/cell_tet4.C...
Compiling C++ (in optimized mode) src/geom/cell_tet.C...
Compiling C++ (in optimized mode) src/geom/edge.C...
Compiling C++ (in optimized mode) src/geom/edge_edge2.C...
Compiling C++ (in optimized mode) src/geom/edge_edge3.C...
Compiling C++ (in optimized mode) src/geom/edge_inf_edge2.C...
Compiling C++ (in optimized mode) src/geom/elem.C...
Compiling C++ (in optimized mode) src/geom/elem_quality.C...
Compiling C++ (in optimized mode) src/geom/elem_refinement.C...
In file included from src/geom/elem_refinement.C:30:
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: ISO C++ forbids
declaration of `hash_multimap' with no type
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: template-id
`hash_multimap<unsigned int, Node*>' used as a declarator
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: parse error
before
`;' token
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:340: 'map_type' is
used
as a type, but is not defined as a type.
make: *** [src/geom/elem_refinement.i686-pc-linux-gnu.o] Error 1
dr. R. van Tol
Computer Simulations and Foundry Processes
tel.:+32 (0)9 2645704 - fax:0032 (0)9 2645848
mailto:rob...@wt... <mailto:rob...@wt...>
WTCM-CRIF Belgian Center of the Technological Industry
Technologiepark 9, B-9052 Gent-Zwijnaarde (Belgium)
tel: +32 (0)9/264 5697
http://www.wtcm.be <http://www.wtcm.be/>
WTCM-CRIF "Your Gateway To Innovation".
Have a look at the future of materials and manufacturing technology
http://techniline.wtcm.be <http://techniline.wtcm.be/>
|
|
From: Rob v. T. <rob...@wt...> - 2004-02-24 13:25:50
|
Dear libmesh users,
I just downloaded the code and I am trying to compile it. I am using Redhat
7 and a GCC-3.0 compiler.
I get an error message:
ISO C++ forbids declaration of `hash_multimap' with no type.
Can anyone tell me how to solve this ??
I have included the configure and make messages below.
Thank you in advance,
Kind regards,
ROB
configuring libMesh -------------
---------------------------------------------
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
<<< C++ compiler is gcc-3.0 >>>
checking how to run the C++ preprocessor... g++ -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for short int... yes
checking size of short int... 2
checking for int... yes
checking size of int... 4
checking for long int... yes
checking size of long int... 4
checking for float... yes
checking size of float... 4
checking for double... yes
checking size of double... 8
checking for void *... yes
checking size of void *... 4
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking whether the compiler implements namespaces... yes
checking whether the compiler has locale... yes
checking whether the compiler has stringstream... yes
checking hash_map usability... no
checking hash_map presence... no
checking for hash_map... no
checking ext/hash_map usability... yes
checking ext/hash_map presence... yes
checking for ext/hash_map... yes
checking hash_set usability... no
checking hash_set presence... no
checking for hash_set... no
checking ext/hash_set usability... yes
checking ext/hash_set presence... yes
checking for ext/hash_set... yes
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
<<< Configuring library with AMR support >>>
<<< Configuring library with expensive data structures enabled >>>
checking rpc/rpc.h usability... yes
checking rpc/rpc.h presence... yes
checking for rpc/rpc.h... yes
<<< Configuring library with XDR support >>>
<<< Configuring library with real number support >>>
<<< Configuring library with reference counting support >>>
checking for ./contrib/netcdf/lib/i686-pc-linux-gnu/libnetcdf.a... no
checking for ./contrib/netcdf/include/netcdf.h... no
---------------------------------------------
----- Configuring for optional packages -----
---------------------------------------------
checking for ./contrib/sfcurves/sfcurves.h... yes
<<< Configuring library with SFC support >>>
checking for ./contrib/gzstream/gzstream.h... yes
<<< Configuring library with gzstreams support >>>
checking for ./contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a... yes
checking for ./contrib/tecplot/include/TECIO.h... yes
<<< Configuring library with Tecplot API support >>>
checking for ./contrib/laspack/lastypes.h... yes
<<< Configuring library with LASPACK version 1.12.3 support >>>
checking for /include/petsc.h... no
checking for /include/mpi.h... no
checking for /lib/libmpich.a... no
checking for ./contrib/metis/Lib/metis.h... yes
<<< Configuring library with Metis support >>>
checking for doxygen... /usr/bin/doxygen
checking for dot... no
----------------------------------------------
--- Done configuring for optional packages ---
----------------------------------------------
checking for perl... /usr/bin/perl
configure: creating ./config.status
config.status: creating Make.common
config.status: creating include/base/libmesh_config.h
configure: creating ./config.status
config.status: creating Make.common
config.status: creating doc/Doxyfile
config.status: creating include/base/libmesh_config.h
config.status: include/base/libmesh_config.h is unchanged
---------------------------------------------
--------- Done Configuring libMesh ----------
---------------------------------------------
[vlr@pc02011 libmesh-0.4.1]$ make
Compiling C++ (in optimized mode) src/base/dof_map.C...
Compiling C++ (in optimized mode) src/base/dof_map_constraints.C...
Compiling C++ (in optimized mode) src/base/dof_object.C...
Compiling C++ (in optimized mode) src/base/equation_systems.C...
Compiling C++ (in optimized mode) src/base/equation_systems_io.C...
Compiling C++ (in optimized mode) src/base/frequency_system.C...
Compiling C++ (in optimized mode) src/base/libmesh.C...
Compiling C++ (in optimized mode) src/base/newmark_system.C...
Compiling C++ (in optimized mode) src/base/node.C...
Compiling C++ (in optimized mode) src/base/reference_counted_object.C...
Compiling C++ (in optimized mode) src/base/reference_counter.C...
Compiling C++ (in optimized mode) src/base/steady_system.C...
Compiling C++ (in optimized mode) src/base/system_base.C...
Compiling C++ (in optimized mode) src/base/system_base_io.C...
Compiling C++ (in optimized mode) src/base/system_base_projection.C...
Compiling C++ (in optimized mode) src/base/transient_system.C...
Compiling C++ (in optimized mode) src/fe/fe_base.C...
Compiling C++ (in optimized mode) src/fe/fe_boundary.C...
Compiling C++ (in optimized mode) src/fe/fe.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_hierarchic_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/fe_interface.C...
Compiling C++ (in optimized mode) src/fe/fe_interface_inf_fe.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_lagrange_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/fe_map.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_1D.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_2D.C...
Compiling C++ (in optimized mode) src/fe/fe_monomial_shape_3D.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_base_radial.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_boundary.C...
Compiling C++ (in optimized mode) src/fe/inf_fe.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_jacobi_20_00_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_jacobi_30_00_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_lagrange_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_legendre_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_map.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_map_eval.C...
Compiling C++ (in optimized mode) src/fe/inf_fe_static.C...
Compiling C++ (in optimized mode) src/geom/cell.C...
Compiling C++ (in optimized mode) src/geom/cell_hex20.C...
Compiling C++ (in optimized mode) src/geom/cell_hex27.C...
Compiling C++ (in optimized mode) src/geom/cell_hex8.C...
Compiling C++ (in optimized mode) src/geom/cell_hex.C...
Compiling C++ (in optimized mode) src/geom/cell_inf.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex16.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex18.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex8.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_hex.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism12.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism6.C...
Compiling C++ (in optimized mode) src/geom/cell_inf_prism.C...
Compiling C++ (in optimized mode) src/geom/cell_prism15.C...
Compiling C++ (in optimized mode) src/geom/cell_prism18.C...
Compiling C++ (in optimized mode) src/geom/cell_prism6.C...
Compiling C++ (in optimized mode) src/geom/cell_prism.C...
Compiling C++ (in optimized mode) src/geom/cell_pyramid5.C...
Compiling C++ (in optimized mode) src/geom/cell_pyramid.C...
Compiling C++ (in optimized mode) src/geom/cell_tet10.C...
Compiling C++ (in optimized mode) src/geom/cell_tet4.C...
Compiling C++ (in optimized mode) src/geom/cell_tet.C...
Compiling C++ (in optimized mode) src/geom/edge.C...
Compiling C++ (in optimized mode) src/geom/edge_edge2.C...
Compiling C++ (in optimized mode) src/geom/edge_edge3.C...
Compiling C++ (in optimized mode) src/geom/edge_inf_edge2.C...
Compiling C++ (in optimized mode) src/geom/elem.C...
Compiling C++ (in optimized mode) src/geom/elem_quality.C...
Compiling C++ (in optimized mode) src/geom/elem_refinement.C...
In file included from src/geom/elem_refinement.C:30:
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: ISO C++ forbids
declaration of `hash_multimap' with no type
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: template-id
`hash_multimap<unsigned int, Node*>' used as a declarator
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:332: parse error before
`;' token
/home/vlr/libmesh-0.4.1/include/mesh/mesh_refinement.h:340: 'map_type' is used
as a type, but is not defined as a type.
make: *** [src/geom/elem_refinement.i686-pc-linux-gnu.o] Error 1
dr. R. van Tol
Computer Simulations and Foundry Processes
tel.:+32 (0)9 2645704 - fax:0032 (0)9 2645848
mailto:rob...@wt...
WTCM-CRIF Belgian Center of the Technological Industry
Technologiepark 9, B-9052 Gent-Zwijnaarde (Belgium)
tel: +32 (0)9/264 5697
http://www.wtcm.be
WTCM-CRIF "Your Gateway To Innovation".
Have a look at the future of materials and manufacturing technology
http://techniline.wtcm.be
|
|
From: Daniel D. <d.d...@tu...> - 2004-02-10 20:48:58
|
On Mon, 9 Feb 2004, KIRK, BENJAMIN (JSC-EG) (NASA) wrote: > As for matrix-free, Daniel has expressed an interest in this in the past. > It would require some extensions to the linear solver interface, but that is > do-able. Yep, i was pretty curious about matrix-free... But then i did some moderately bigger systems, and saw that for our exterior acoustics thing, matrix-free is not really necessary. Really building the matrix is not "just doable", but it helps a lot handling the matrix, when you want some special preconditioners, you may need it explicitly. So, honestly, matrix-free is off my list... But i am still hoping to find time for helping in the eigenthingy-regime. Daniel > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users > |
|
From: John P. <pet...@cf...> - 2004-02-09 18:15:24
|
seid mehdi bostandoust nik writes: > Hi > Based on hughes,Tezduyar and others it is possible to > solve Navier-Stokes equations with iterative solvers > by the help of element by element preconditioning. > > I am using petsc and currently in Petsc there is not > element by element preconditioning(it is said that > this feature may be added to PETSC3.0). > I want to know that does the libmesh solver support > element by element preconditioning for iterative > solvers or not? We use a global element stiffness matrix instead of an element-by-element approach. All of the solvers are set up to form a global (distributed) matrix and then perform a global solve. The element matrices are of the DenseMatrix type defined by the library and currently do not implement any sort of preconditioning. -John |
|
From: KIRK, B. (JSC-E. (NASA) <ben...@na...> - 2004-02-09 18:13:53
|
As I remember it, Hughes, Tezduyar, and others use an element-by-element matrix-free GMRES approach. In this approach the global matrix is never formed, and each time a matrix-vector product is needed the element matrix assembly routine (or a functional equivalent) is called. This is more memory-efficient but more computationally-expensive that assembling the global matrix and preconditioning it. In libMesh the global matrix is assembled, and it may be preconditioned as you see fit. This is generally better than element-by-element preconditioning. However, if you want to perform element-by-element preconditioning you can certainly precondition the element matrix (after you assemble it in your code) before you insert it into the global matrix. As for matrix-free, Daniel has expressed an interest in this in the past. It would require some extensions to the linear solver interface, but that is do-able. Does this help? -Ben -----Original Message----- From: lib...@li... [mailto:lib...@li...] On Behalf Of seid mehdi bostandoust nik Sent: Monday, February 09, 2004 12:02 PM To: lib...@li...; lib...@li... Subject: [Libmesh-devel] element by element preconditioning? Hi Based on hughes,Tezduyar and others it is possible to solve Navier-Stokes equations with iterative solvers by the help of element by element preconditioning. I am using petsc and currently in Petsc there is not element by element preconditioning(it is said that this feature may be added to PETSC3.0). I want to know that does the libmesh solver support element by element preconditioning for iterative solvers or not? thanks bye __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Libmesh-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libmesh-devel |
|
From: seid m. b. n. <mbo...@ya...> - 2004-02-09 18:01:46
|
Hi Based on hughes,Tezduyar and others it is possible to solve Navier-Stokes equations with iterative solvers by the help of element by element preconditioning. I am using petsc and currently in Petsc there is not element by element preconditioning(it is said that this feature may be added to PETSC3.0). I want to know that does the libmesh solver support element by element preconditioning for iterative solvers or not? thanks bye __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html |
|
From: Kevin E. <kel...@am...> - 2004-02-08 21:40:35
|
John Peterson wrote:
>Kevin Ellwood writes:
> > John Peterson wrote:
> >
> > >Hi. In fact we have seen something like that before. Could you
> > >post the result of the entire $(INCLUDES) Make variable? In the
> > >previous case, the $(INCLUDES) looked something like:
> > >
> > >-I/valid/path/one -I/valid/path/two -I -I/all/remaining/paths/invalid
> > >
> > >where the "naked" -I causes all the following include directories
> > >to be messed up. That might be the problem in your case...
> > >
> > >-John
> > >
> > >Kevin Ellwood writes:
> > > > Hi All,
> > > >
> > > > I am trying to install libmesh at home and I am having
> > > > a problem that has me befuddled. I tried many times
> > > > but the basic:
> > > >
> > > > ./configure
> > > > make
> > > >
> > > > should work, I think. I have PETSC installed in
> > > > /usr/local/petsc-2.1.6 and PETSC_DIR is set as is
> > > > PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is
> > > > version 3.2.2.
> > > >
> > > > "make" chugs along without issue until:
> > > > Compiling C++ (in optimized mode) src/mesh/mesh.C...
> > > > src/mesh/mesh.C:35:22: sfcurves.h: No such file or
> > > > directory
> > > > make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1
> > > >
> > > > The odd thing is that the actual compile command has
> > > > -I/home/kellwood/libmesh-0.4.1/contrib/sfcurves and:
> > > >
> > > > ls /home/kellwood/libmesh-0.4.1/contrib/sfcurves
> > > > cmp.c hilbert.c Makefile morton.c README
> > > > sfcurves.h sfcurves_internal.h
> > > >
> > > > Finally, when I copy sfcurves.h to src/mesh, it
> > > > proceeds past mesh.C without problems.
> > > >
> > > > Has anyone experience such oddness? I know it is not
> > > > a libmesh issue but it is very strange. Incidentally,
> > > > I tried it on a linux box at work (RH9) and exactly
> > > > the same thing happened.
> > >
> > Hi John
> >
> > Below is the relevant part of make echo. The petsc part of the include
> > seems correct "-I/usr/local/petsc-2.1.6/include
> > -I/usr/local/petsc-2.1.6/bmake/linux-gnu".
> >
> > Thanks
> > Kevin
> >
> > CFLAGS:
> > -O2 -felide-constructors -DNDEBUG -fPIC -funroll-loops -fstrict-aliasing
> > -DPETSC_USE_DYNAMIC_LIBRARIES
> >
> > CXXFLAGS:
> > -O2 -felide-constructors -DNDEBUG -fPIC -funroll-loops -fstrict-aliasing
> > -DPETSC_USE_DYNAMIC_LIBRARIES
> >
> > INCLUDE:
> > -I/home/kellwood/development/libmesh/include/base
> > -I/home/kellwood/development/libmesh/include/enums
> > -I/home/kellwood/development/libmesh/include/fe
> > -I/home/kellwood/development/libmesh/include/geom
> > -I/home/kellwood/development/libmesh/include/mesh
> > -I/home/kellwood/development/libmesh/include/numerics
> > -I/home/kellwood/development/libmesh/include/partitioning
> > -I/home/kellwood/development/libmesh/include/quadrature
> > -I/home/kellwood/development/libmesh/include/solvers
> > -I/home/kellwood/development/libmesh/include/utils
> > -I/home/kellwood/development/libmesh/contrib/laspack
> > -I/home/kellwood/development/libmesh/contrib/metis/Lib
> > -I/home/kellwood/development/libmesh/contrib/parmetis/Lib
> > -I/home/kellwood/development/libmesh/contrib/sfcurves
> > -I/home/kellwood/development/libmesh/contrib/gzstream
> > -I/home/kellwood/development/libmesh/contrib/tecplot/include
> > -I/usr/local/petsc-2.1.6/include
> > -I/usr/local/petsc-2.1.6/bmake/linux-gnu -I/usr/include -I/usr/include
> >
> > LIBS:
> > /home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt/libmesh.so
> > /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/liblaspack.so
> > /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libmetis.so
> > /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libparmetis.so
> > /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libsfcurves.so
> > /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libgzstream.so
> > -lz
> > /home/kellwood/development/libmesh/contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a
> > -L/usr/local/petsc-2.1.6/lib/libO/linux-gnu -lpetscsles -lpetscdm
> > -lpetscmat -lpetscvec -lpetsc -L/usr/lib -llapack -lblas -L/usr/lib
> > -lmpich -lpmpich -L/usr/X11R6/lib -lX11
> > -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3
> > -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../../i686-pc-linux-gnu/lib
> > -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../.. -lfrtbegin -lg2c -lm
> > -lgcc_s -L/usr/lib -lmpich -lpmpich
> > -Wl,-rpath,/home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt
> > -Wl,-rpath,/home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt
> > -Wl,-rpath,/usr/local/petsc-2.1.6/lib/libO/linux-gnu
> >
> > LDFLAGS:
> >
> >
> > DLFLAGS:
> > -Wl,-rpath,/home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt
> > -Wl,-rpath,/home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt
> > -Wl,-rpath,/usr/local/petsc-2.1.6/lib/libO/linux-gnu
>
>
>It looks like everything is correct, as you stated. I'm really not sure
>what the problem is. Are you by any chance using the uni-processor MPI
>that comes with Petsc, or have you installed the full mpich distribution.
>I don't think that is really the problem, but we have had an issue with
>incorrect Make paths in the past which I believe we traced back to that.
>
>-John
>
>
>
I've installed PETSC with mpich, though I haven't got the multiprocessor
examples to run. My own PETSC code runs as a single process. The
multiprocess prblem is related to the fact that my "newly installed"
gentoo distro uses ssh only (no rsh). I've got to get that one figured
out but I don't think that is the issue. I'll try to dig more on my own.
Thanks
Kevin
--
.*.
Kevin R.J. Ellwood /V\
+-+-+-+-+-+-+ +-+-+-+-+-+ (/ \)
|g|e|n|t|o|o| |l|i|n|u|x| ( )
+-+-+-+-+-+-+ +-+-+-+-+-+ ^^_^^
|
|
From: Kevin E. <kel...@am...> - 2004-02-08 20:14:08
|
John Peterson wrote: >Hi. In fact we have seen something like that before. Could you >post the result of the entire $(INCLUDES) Make variable? In the >previous case, the $(INCLUDES) looked something like: > >-I/valid/path/one -I/valid/path/two -I -I/all/remaining/paths/invalid > >where the "naked" -I causes all the following include directories >to be messed up. That might be the problem in your case... > >-John > >Kevin Ellwood writes: > > Hi All, > > > > I am trying to install libmesh at home and I am having > > a problem that has me befuddled. I tried many times > > but the basic: > > > > ./configure > > make > > > > should work, I think. I have PETSC installed in > > /usr/local/petsc-2.1.6 and PETSC_DIR is set as is > > PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is > > version 3.2.2. > > > > "make" chugs along without issue until: > > Compiling C++ (in optimized mode) src/mesh/mesh.C... > > src/mesh/mesh.C:35:22: sfcurves.h: No such file or > > directory > > make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1 > > > > The odd thing is that the actual compile command has > > -I/home/kellwood/libmesh-0.4.1/contrib/sfcurves and: > > > > ls /home/kellwood/libmesh-0.4.1/contrib/sfcurves > > cmp.c hilbert.c Makefile morton.c README > > sfcurves.h sfcurves_internal.h > > > > Finally, when I copy sfcurves.h to src/mesh, it > > proceeds past mesh.C without problems. > > > > Has anyone experience such oddness? I know it is not > > a libmesh issue but it is very strange. Incidentally, > > I tried it on a linux box at work (RH9) and exactly > > the same thing happened. > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >Libmesh-users mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libmesh-users > > > Hi John Below is the relevant part of make echo. The petsc part of the include seems correct "-I/usr/local/petsc-2.1.6/include -I/usr/local/petsc-2.1.6/bmake/linux-gnu". Thanks Kevin CFLAGS: -O2 -felide-constructors -DNDEBUG -fPIC -funroll-loops -fstrict-aliasing -DPETSC_USE_DYNAMIC_LIBRARIES CXXFLAGS: -O2 -felide-constructors -DNDEBUG -fPIC -funroll-loops -fstrict-aliasing -DPETSC_USE_DYNAMIC_LIBRARIES INCLUDE: -I/home/kellwood/development/libmesh/include/base -I/home/kellwood/development/libmesh/include/enums -I/home/kellwood/development/libmesh/include/fe -I/home/kellwood/development/libmesh/include/geom -I/home/kellwood/development/libmesh/include/mesh -I/home/kellwood/development/libmesh/include/numerics -I/home/kellwood/development/libmesh/include/partitioning -I/home/kellwood/development/libmesh/include/quadrature -I/home/kellwood/development/libmesh/include/solvers -I/home/kellwood/development/libmesh/include/utils -I/home/kellwood/development/libmesh/contrib/laspack -I/home/kellwood/development/libmesh/contrib/metis/Lib -I/home/kellwood/development/libmesh/contrib/parmetis/Lib -I/home/kellwood/development/libmesh/contrib/sfcurves -I/home/kellwood/development/libmesh/contrib/gzstream -I/home/kellwood/development/libmesh/contrib/tecplot/include -I/usr/local/petsc-2.1.6/include -I/usr/local/petsc-2.1.6/bmake/linux-gnu -I/usr/include -I/usr/include LIBS: /home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt/libmesh.so /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/liblaspack.so /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libmetis.so /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libparmetis.so /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libsfcurves.so /home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt/libgzstream.so -lz /home/kellwood/development/libmesh/contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a -L/usr/local/petsc-2.1.6/lib/libO/linux-gnu -lpetscsles -lpetscdm -lpetscmat -lpetscvec -lpetsc -L/usr/lib -llapack -lblas -L/usr/lib -lmpich -lpmpich -L/usr/X11R6/lib -lX11 -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3 -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../../../i686-pc-linux-gnu/lib -L/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/../../.. -lfrtbegin -lg2c -lm -lgcc_s -L/usr/lib -lmpich -lpmpich -Wl,-rpath,/home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt -Wl,-rpath,/home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt -Wl,-rpath,/usr/local/petsc-2.1.6/lib/libO/linux-gnu LDFLAGS: DLFLAGS: -Wl,-rpath,/home/kellwood/development/libmesh/lib/i686-pc-linux-gnu_opt -Wl,-rpath,/home/kellwood/development/libmesh/contrib/lib/i686-pc-linux-gnu_opt -Wl,-rpath,/usr/local/petsc-2.1.6/lib/libO/linux-gnu -- .*. Kevin R.J. Ellwood /V\ +-+-+-+-+-+-+ +-+-+-+-+-+ (/ \) |g|e|n|t|o|o| |l|i|n|u|x| ( ) +-+-+-+-+-+-+ +-+-+-+-+-+ ^^_^^ |
|
From: John P. <pet...@cf...> - 2004-02-08 03:24:05
|
Hi. In fact we have seen something like that before. Could you post the result of the entire $(INCLUDES) Make variable? In the previous case, the $(INCLUDES) looked something like: -I/valid/path/one -I/valid/path/two -I -I/all/remaining/paths/invalid where the "naked" -I causes all the following include directories to be messed up. That might be the problem in your case... -John Kevin Ellwood writes: > Hi All, > > I am trying to install libmesh at home and I am having > a problem that has me befuddled. I tried many times > but the basic: > > ./configure > make > > should work, I think. I have PETSC installed in > /usr/local/petsc-2.1.6 and PETSC_DIR is set as is > PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is > version 3.2.2. > > "make" chugs along without issue until: > Compiling C++ (in optimized mode) src/mesh/mesh.C... > src/mesh/mesh.C:35:22: sfcurves.h: No such file or > directory > make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1 > > The odd thing is that the actual compile command has > -I/home/kellwood/libmesh-0.4.1/contrib/sfcurves and: > > ls /home/kellwood/libmesh-0.4.1/contrib/sfcurves > cmp.c hilbert.c Makefile morton.c README > sfcurves.h sfcurves_internal.h > > Finally, when I copy sfcurves.h to src/mesh, it > proceeds past mesh.C without problems. > > Has anyone experience such oddness? I know it is not > a libmesh issue but it is very strange. Incidentally, > I tried it on a linux box at work (RH9) and exactly > the same thing happened. |
|
From: John P. <pet...@cf...> - 2004-02-08 03:20:03
|
Benjamin S. Kirk writes: > Thanks for the prompt on this! > > Many of the changes in CVS simply changed "Copyright 2002-2003" with > "2002-2004" > > However, there are a number of other functional changes as well. I > guess I can put together an official release this week (comments from > the devel list?). The biggest job in creating an "official" release is > in testing the code on all the machines I have access to, and testing > various configuration options. > > I'll try to release 0.4.2 this week if there are no complaints from the > other developers. No complaints. I think I am almost ready to check in the nonlinear example 13. I'm just ironing out what will give the best results in the least amount of work so that the examples can still run quickly. -John |
|
From: Benjamin S. K. <be...@cf...> - 2004-02-08 00:54:22
|
Thanks for the prompt on this! Many of the changes in CVS simply changed "Copyright 2002-2003" with "2002-2004" However, there are a number of other functional changes as well. I guess I can put together an official release this week (comments from the devel list?). The biggest job in creating an "official" release is in testing the code on all the machines I have access to, and testing various configuration options. I'll try to release 0.4.2 this week if there are no complaints from the other developers. -Ben Denis Danilov wrote: >Hi, > >According CVS i see many things have been changed in >comparison with libmesh-0.4.1. Is there any plans about >next stable release of libmesh in near future? > >Best regards, >Denis > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >Libmesh-users mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libmesh-users > > |
|
From: Daniel D. <d.d...@tu...> - 2004-02-07 15:19:21
|
Hi, first of all: what do you need the definition for? When you have some other file format, i'd recommend to look at the other mesh importers, there are some. Provided you answer the first question, after a short moment of thought, still with 'yes', do this: - in the libmesh dir, change to reference_elements, chose the element you want, - open file src/mesh/mesh_xdr_support.C in an editor - open http://libmesh.sourceforge.net/doxygen/classHex27.html (or whatever element you want) in a browser, see the rather self-explanatory perspective drawing of the element, - take a sheet of paper, sketch the element you want, number it as you want, - and walk through the code, line by line, see what happens. This is pretty much it, just do it. btw: xda is just plain ASCII, while xdr is the datastream, but binary. So don't be confused about the switch statements concerned with the different r/w modes. Sorry for the ironic touch of this mail, but for next time i'd recommend to check all the documentation (as explained above). The great advantage of libmesh is: it's open source, so you can directly see what happens (and what kind of sometimes weird, sometimes beautiful code is in there). Taking a look at src/mesh/mesh_xdr_support.C, it will directly tell you what e.g. "Num. Element Blocks" means. This will help you much more, because then you yourself can answer your questions, and you do not depend on someone else. When you still end up in a pit, just feel free to ask. -- Be curious, have fun! Daniel | | Daniel Dreyer, SM (MIT) | AUDI AG, Ingolstadt, Germany On Wed, 28 Jan 2004, seid mehdi bostandoust nik wrote: > Hi > I ran the ex1 example and I have some questions. > I am sorry to ask too much. > The one_quad.xda file have some parameters that I > could not understand them.they are as follows: > what does "Num. Element Blocks" mean? > what does Element types in each block mean?(actually > where can I find the definition of Element types for > example quad=5) > There is a line "0 1 2 3" in this file,what does it > mean? > There is an extra column after the coordinates,is it > used for marking for boundary conditions?(if yes where > can I find the definition of boundary conditions and > their appropriate values?) > In the last part there are some numbers.Is it possible > let me know the definition of them? > 0 0 0 > 0 1 1 > 0 2 2 > 0 3 3 > > I look forward to hearing from you > > Best Regard > > Bostandoost > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free web site building tool. Try it! > http://webhosting.yahoo.com/ps/sb/ > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users > |
|
From: Denis D. <dan...@ya...> - 2004-02-07 14:51:47
|
Hi, According CVS i see many things have been changed in comparison with libmesh-0.4.1. Is there any plans about next stable release of libmesh in near future? Best regards, Denis |
|
From: KIRK, B. (JSC-E. (NASA) <ben...@na...> - 2004-02-06 15:35:14
|
This is gonna be ugly, but post the contents of 'make echo' and let me see what all the compiler flags are... My guess is there is an empty '-I' before the sfcurves include path. This would be caused, perhaps, by misconfiguration: maybe configure enabled an option but did not properly set the include path... If that's the case then I would classify it as a libmesh issue... :-) -Ben -----Original Message----- From: lib...@li... [mailto:lib...@li...] On Behalf Of Kevin Ellwood Sent: Friday, February 06, 2004 9:24 AM To: lib...@li... Subject: [Libmesh-users] Odd compiling problem with libmesh 0.4.1 Hi All, I am trying to install libmesh at home and I am having a problem that has me befuddled. I tried many times but the basic: ./configure make should work, I think. I have PETSC installed in /usr/local/petsc-2.1.6 and PETSC_DIR is set as is PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is version 3.2.2. "make" chugs along without issue until: Compiling C++ (in optimized mode) src/mesh/mesh.C... src/mesh/mesh.C:35:22: sfcurves.h: No such file or directory make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1 The odd thing is that the actual compile command has -I/home/kellwood/libmesh-0.4.1/contrib/sfcurves and: ls /home/kellwood/libmesh-0.4.1/contrib/sfcurves cmp.c hilbert.c Makefile morton.c README sfcurves.h sfcurves_internal.h Finally, when I copy sfcurves.h to src/mesh, it proceeds past mesh.C without problems. Has anyone experience such oddness? I know it is not a libmesh issue but it is very strange. Incidentally, I tried it on a linux box at work (RH9) and exactly the same thing happened. Thanks Kevin ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Libmesh-users mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libmesh-users |
|
From: Kevin E. <kel...@am...> - 2004-02-06 15:24:35
|
Hi All, I am trying to install libmesh at home and I am having a problem that has me befuddled. I tried many times but the basic: ./configure make should work, I think. I have PETSC installed in /usr/local/petsc-2.1.6 and PETSC_DIR is set as is PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is version 3.2.2. "make" chugs along without issue until: Compiling C++ (in optimized mode) src/mesh/mesh.C... src/mesh/mesh.C:35:22: sfcurves.h: No such file or directory make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1 The odd thing is that the actual compile command has -I/home/kellwood/libmesh-0.4.1/contrib/sfcurves and: ls /home/kellwood/libmesh-0.4.1/contrib/sfcurves cmp.c hilbert.c Makefile morton.c README sfcurves.h sfcurves_internal.h Finally, when I copy sfcurves.h to src/mesh, it proceeds past mesh.C without problems. Has anyone experience such oddness? I know it is not a libmesh issue but it is very strange. Incidentally, I tried it on a linux box at work (RH9) and exactly the same thing happened. Thanks Kevin |
|
From: Benjamin S. K. <be...@cf...> - 2004-01-31 14:49:21
|
This is a problem with the PGI C++ compier, and there is currently no work-around. The problem is that the PGI compiler gives template instantiations internal linkage, which means that these symbols cannot be seen outside of the file it was instantiated in. I have recently taken a job at NASA, and we have a number of licenses for PGI products. So, I am now in a position where they might actually fix the problems I report. I spoke with the head of their support department at Supercomputing 2003 (in November) and he told me they focus on FORTRAN, so my bug wasn't a high-priority. In the meantime, you should be able to compile the C++ sections of the code with g++ or icc and link with PETSc that has been built with the PGI compilers. Under bash, do CXX=icc CC=icc F77=pgf77 ./configure ... Let me know if this will work for you. I'll bug the PGI people again... -Ben Buffat Marc wrote: >Hello >I am trying to port my development project (FV on unstructured mesh) with >libmesh on a linux cluster running RH 7.2 with PGI compiler (Portland group). >(The project is developped and runs on a biP4 RH9.0) >PETSC compile and run without problem with pgCC on the cluster >but I got problem with libmesh and PGI pgCC C++ compiler with the template >During the link process I got the following message > >C++ prelinker: error: "int NumericVector<T1>::compare(const NumericVector<T1> >&, double) const [with T1=double]" has been referenced as both an explicit >specialization and a generated instantiation >C++ prelinker: error: "double FE<N1, N2>::shape(const Elem *, >libMeshEnums::Order, unsigned int, const Point &) [with N1=(unsigned int)2, >N2=(libMeshEnums::FEFamily)1]" has been referenced as both an explicit >specialization and a generated instantiation >.... > >I have tried both the static and dynamic lib. >Any idea would be appreciated > Marc > > |
|
From: Buffat M. <bu...@uf...> - 2004-01-31 01:41:25
|
Hello I am trying to port my development project (FV on unstructured mesh) with libmesh on a linux cluster running RH 7.2 with PGI compiler (Portland group). (The project is developped and runs on a biP4 RH9.0) PETSC compile and run without problem with pgCC on the cluster but I got problem with libmesh and PGI pgCC C++ compiler with the template During the link process I got the following message C++ prelinker: error: "int NumericVector<T1>::compare(const NumericVector<T1> &, double) const [with T1=double]" has been referenced as both an explicit specialization and a generated instantiation C++ prelinker: error: "double FE<N1, N2>::shape(const Elem *, libMeshEnums::Order, unsigned int, const Point &) [with N1=(unsigned int)2, N2=(libMeshEnums::FEFamily)1]" has been referenced as both an explicit specialization and a generated instantiation .... I have tried both the static and dynamic lib. Any idea would be appreciated Marc -- Marc BUFFAT, Pr. Universite Claude Bernard LYON I tel: (33) 04/72/43/11/02 (UCBL) fax: (33) 04/72/44/80/54 bu...@uf... | http://p2chpd-cluster.univ-lyon1.fr |
197 messages has been excluded from this view by a project administrator.
