From: Frank L. <fra...@go...> - 2009-06-29 13:12:48
|
2009/6/29 W. Michael Petullo <mi...@fl...>: >> Anyhow: I'm currently improving the db-check macro so that in >> cross-compiation mode the value from --with-bdb is only checked for >> the presence of the necessary files (header and lib). That would >> result in one interface regardless of compilation mode. When cross >> compiling you would just have to ensude that bdb is installed at the >> same location at host and build machine. Would that be ok? > > But the run-time requirement would be resolved by the dynamic linker, > right? Most likely, libdb.so would not be in the same spot on the host and > build machine (i.e., it can't go in build's /usr/lib because it is not for > the correct architecture). Yes, the _paths_ would have to be the same. But when cross-compiling the patched macro won't _use_ e.g. link to the lib found there. It will only check for the presence and record the path. As said the main benefit would be to have the same simple optin (--with=bdb) for both compilation cases without the necessity to fiddle with anything else. Another possible albeit completly different and simple solution would be to check if BDB_CFLAGS, BDB_LIBS, BDB_BIN and BDB_PATH are already set and if theya re completly skip all checks. -Frank |