On Thu, Dec 30, 2010 at 08:47, Rich Shepard <[email protected]> wrote: > I guess all the academics on the GRASS mail list are off since > universities world-wide are closed, so I'll see if coders here can help me > resolve an inability to configure the Makefile prior to building. > > When I run ./configure with all the necessary options (and all previous > builds have not had problems finding libraries or headers for postgres or > sqlite), it fails with these messages: > > checking for location of SQLite library... /usr/lib/ > checking for sqlite3_open in -lsqlite3... no > checking for sqlite3_open in -lsqlite3... no > configure: error: *** Unable to locate SQLite library.
so what does config.log say? that's where you'll find the actual output from the tests, including stderr that might tell you about missing files, compilation troubles, and indeed even show you the code that configure is attempting to compile before throwing that error. (i make the assumption that this test is a compilation test--most that ./configure does are, even just checking for include files is usually done not by looking for the file on the filesystem but trying to use it in via the compiler in some dummy code) config.log will often include line numbers from the ./configure script for your further edification. that script is never fun to debug, but you can often see what is going on in it and adjust the system (or the ./configure script) appropriately. if you're going to include config.log here, don't send us the whole file, just the part where the last tests fail. you can leave off the last many lines too--we don't need to know all the values of the variables and all that jazz, just what the script is running right before it announces those failures (should include code, a command line for compiling, and the output from that attempt). _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
