On Sep 21, 2013, at 1:10 AM, Geert Janssens <janssens-ge...@telenet.be> wrote:
> Would it make sense to also point out the other option here: disable dbi
> support again by
> dropping the --enable_dbi option ?
OK.
On Sep 21, 2013, at 2:45 AM, Geert Janssens <janssens-ge...@telenet.be> wrote:
> And in addition to my previous comment: this code actually breaks configure
> on my system
> (Fedora 19, 64 bit):
>
> checking dbi/dbi.h usability... yes
> checking dbi/dbi.h presence... yes
> checking for dbi/dbi.h... yes
> src/optional/python-bindings/Makefile.am:117: warning: filter-out
> gnucash_core_c.py,
> ${PYTHON_LINK_FILES}: non-POSIX variable name
> src/optional/python-bindings/Makefile.am:117: (probably a GNU make extension)
> checking Looking for at least one supported DBD module...
> configure: error: in `/home/janssege/Development/Builds/gnucash-f19-trunk':
> configure: error:
> Unable to find any of the supported dbd modules (libdbdsqlite3, libdbdmysql,
> or libdbdpgsql)
> needed to actually use the SQL backend. Please install one or more of them to
> proceed.
>
> See `config.log' for more details
> make: *** [config.status] Error 1
> make: *** Waiting for unfinished jobs....
Hmm. I tested on debian, not fedora, and I don't yet have a fedora-19 VM.
Can you look in config.log and see what failed?
Regards,
John Ralls
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
