1) BerkeleyDbDatastore.cpp - generates about 50 errors for undeclared functions and structs, even though all the include files are present. An example of the errors follows:
In file included from BerkeleyDbDatastore.cpp:25:
/Users/wkirkham/OpenSees/SRC/database/BerkeleyDbDatastore.h:89: error: syntax
error before `*' token
/Users/wkirkham/OpenSees/SRC/database/BerkeleyDbDatastore.h:48: error: `NULL'
was not declared in this scope
BerkeleyDbDatastore.cpp: In constructor `
BerkeleyDbDatastore::BerkeleyDbDatastore(const char*, Domain&,
FEM_ObjectBroker&, char*)':
BerkeleyDbDatastore.cpp:60: error: `dbenv' undeclared (first use this function)
BerkeleyDbDatastore.cpp:60: error: (Each undeclared identifier is reported only
once for each function it appears in.)
BerkeleyDbDatastore.cpp:60: error: `db_env_create' undeclared (first use this
function)
BerkeleyDbDatastore.cpp:62: error: `db_strerror' undeclared (first use this
function)
BerkeleyDbDatastore.cpp:71: error: `DB_CREATE' undeclared (first use this
function)
and it continues for a while. Can anyone verify whether the current download file has the correct includes?
2) It appears the the installation of Tcl/Tk is somewhat different under 8.4.6 than under 8.3, which appears in the Makfile.def for MacOSX. It seems to build dynamic libs rather than static libs. At least I think that's the problem. When I get to the linking step, I get the following messages:
LIBRARIES BUILT ... NOW LINKING OpenSees PROGRAM
wkirkham William-Kirkhams-Computer.local 7.4.0 Darwin Tue Jun 22 09:12:50 PDT 2004
gnumake[1]: Nothing to be done for `tcl'.
gnumake[2]: Nothing to be done for `tcl'.
g++: /Users/wkirkham/lib/libOpenSees.a: No such file or directory
g++: /Users/wkirkham/lib/libReliability.a: No such file or directory
So, even though OpenSees is all compiled, nothing seems to be needed for Tcl, so there is no OpenSees.a library. Has anyone had this experience?
3) Just out of curiousity, is anyone currently using OpenSees on a Mac or on anything outside of the Berkeley enviroment? I am a little suspicious that the BerkeleyDbDatastore problems could be more significant if the program depends on some Berkeley specific MySQL implementation.
Thanks for your help!