I've not hit this error when I last built -6.5, and the sqlite libs are in
/usr/lib/. I think I need to refine the location in the configure file, but
want to check here first.
The error is:
checking for location of SQLite library... checking for sqlite3_open in -lsqlite3... no
checking for sqlite3_open in -lsqlite3... no
configure: error: *** Unable to locate SQLite library.
I've not hit this error when I last built -6.5, and the sqlite libs are in
/usr/lib/.
OK.
I think I need to refine the location in the configure file, but
want to check here first.
The error is:
checking for location of SQLite library... checking for sqlite3_open in
-lsqlite3... no
checking for sqlite3_open in -lsqlite3... no
configure: error: *** Unable to locate SQLite library.
checking whether to use Cairo... yes
checking for location of cairo includes... checking for cairo.h... yes
checking for location of cairo library... checking for cairo linking flags... checking for cairo_create... no
configure: error: *** Unable to locate .
checking whether to use Cairo... yes
checking for location of cairo includes... checking for cairo.h... yes
checking for location of cairo library... checking for cairo linking flags... checking for cairo_create... no
configure: error: *** Unable to locate .
Well, this is fixed. I upgraded cairomm (the C++ wrapper to cairo) from
1.6.4 to 1.8.0 and the code configured and built.
Not OK, should be --with-sqlite-libs=/usr/lib if the sqlite libs are in /usr/lib
It should never be necessary to specify /usr/lib or /usr/include
explicitly, and may be counter-productive (mainly with older versions
of gcc on platforms where it is not the "official" compiler).
> This morning I see a new error:
>
> checking whether to use Cairo... yes
> checking for location of cairo includes... checking for cairo.h... yes
> checking for location of cairo library... checking for cairo linking flags...
> checking for cairo_create... no
> configure: error: *** Unable to locate .
Well, this is fixed. I upgraded cairomm (the C++ wrapper to cairo) from
1.6.4 to 1.8.0 and the code configured and built.
That's coincidence; GRASS doesn't use cairomm.
For future reference: if you get configure errors, look at the bottom
of config.log. It will list the exact test being performed and any
error messages which were generated.
It should never be necessary to specify /usr/lib or /usr/include
explicitly, and may be counter-productive (mainly with older versions of
gcc on platforms where it is not the "official" compiler).
Glynn,
I had not before specified the location of the sqlite libs, but did
specify /usr/lib and /usr/include. Suggestions in the configure file were
not clear on whether to include them so I did. Removing those explicit
inclusions, and updating to the latest sqlite3 and cairomm fixed what
irritated the configure file yesterday.
For future reference: if you get configure errors, look at the bottom of
config.log. It will list the exact test being performed and any error
messages which were generated.
Almost always I see the same messages at the end of the log as I do when
configure bails out. But, this is good advice and I thank you.
Just to clarify - You have to read FILE named config.log at source
directory and look for last compilation command (i.e. gcc blabla). It
will give information WHY test failed and not simply WHICH one failed.
For future reference: if you get configure errors, look at the bottom of
config.log. It will list the exact test being performed and any error
messages which were generated.
Almost always I see the same messages at the end of the log as I do when
configure bails out. But, this is good advice and I thank you.