ID: 51005
Updated by: [email protected]
Reported By: geissert at debian dot org
Status: Analyzed
Bug Type: *Compile Issues
PHP Version: 5.3.1
New Comment:
Yes, I am aware of that, but it is --without-sqlite3 there because by
default if you don't specify anything you get sqlite3 compiled in since
we bundle that library. So when you do ./configure --help you should
see --without-sqlite3 as the listed option letting you know to use that
to build PHP without it.
Previous Comments:
------------------------------------------------------------------------
[2010-02-10 23:00:05] geissert at debian dot org
Sorry for not being specific, I was talking about the description on
the m4 file:
PHP_ARG_WITH(sqlite3, whether to enable the SQLite3 extension,
[ --without-sqlite3[=DIR] Do not include SQLite3 support. DIR is the
prefix to
SQLite3 installation directory.], yes)
------------------------------------------------------------------------
[2010-02-10 22:32:35] [email protected]
The option is called --with-sqlite3. That's how autoconf works. You
have --enable/--disable and --with/--without switches. If the feature
is on by default then you use --disable/--without to turn it off. If
the feature is off by default, then it is the opposite. Try it by
using --with-sqlite3=/some/path
But yes, the yes/no responses are messed up when using these.
------------------------------------------------------------------------
[2010-02-10 22:09:56] geissert at debian dot org
Description:
------------
I just noticed sqlite3's config0.m4 has an inverted logic:
--without-sqlite3 defaults to yes, which instead of NOT including
sqlite3 it _does_ include it (using the bundled copy).
--without-sqlite3=/foo also makes it include the extension, looking for
the headers under /foo
--without-sqlite3=no does not include it.
IOW: the option should be called --with-sqlite3, not --without-sqlite3
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=51005&edit=1
