This used to add -L/lib to LDFLAGS which was not an issue unless
you are cross compiling and then it may detect PCRE features based
on the host PCRE not the target one.
While cross-compiling; bin2c and ptimec need to run during build on the
build-host. Currently; the host compiler is picked and the generated
binaries cannont be exec'ed causing the build to fail.
The change fixes the bin2c and ptimec compilation units to use the
build host compatible compiler.
The code to handle in-memory db exceptions is hideous and unreliable,
given the fact that SQLite does not expose much in terms of getting the
current value and the methods to check the compile time options can
themselves be disabled by a compile=time option in SQLite.
There really isn't much use for in-memory databases and if someone
really needs it, they can always choose to run in normal mode, so just
remove the extra code.
This fixeststack/lnav#253
The libcurl.m4 macros will still continue to look for a static archive
for libcurl but if one is not found and the binary is being compiled on
OS X, they will pick up the dynamic library if one is available.
* Remove some of the obsolete macros.
* Use AC_CONFIG_MACRO_DIR to allow compatibility with older versions of
autoconf.
* Remove AU_ALIAS from curses macro.
On some systems, sqlite3 requires pthread libraries to be linked in. Add
the flag so that autoconf can successfully compile and look for
'sqlite3_open'.
The current macro does not seem to honor the CFLAGS and LDFLAGS
variables if '--with-sqlite3=yes' is used. Fix this and some of
the other cruft in the macro.
On FreeBSD variant, readline functionality is provided by editline which
is almost compatible but not quite. We could do a specific check for
editline but if editline adds the functionality in the future, this
check will still continue to fail. Instead look for one of the symbols
currently missing in editline as a sanity check.
The macro does not track the include directory when it is passed in
using the '--with-readline=/foo/bar' invocation of '--with-readline'
flag.
This change should fix the problem. I've tried to keep the functionality
exactly the same as before and converted the script to pure M4sh, which
should produce a more portable configure script.
