Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 870782 Details for
Bug 914346
dev-db/libdbi-drivers-0.9.0-r1 - install: cannot stat ./.../ : No such file or directory
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
dev-db:libdbi-drivers-0.9.0-r1:20230917-022040.log
dev-db:libdbi-drivers-0.9.0-r1:20230917-022040.log (text/plain), 124.68 KB, created by
Toralf Förster
on 2023-09-17 08:44:13 UTC
(
hide
)
Description:
dev-db:libdbi-drivers-0.9.0-r1:20230917-022040.log
Filename:
MIME Type:
Creator:
Toralf Förster
Created:
2023-09-17 08:44:13 UTC
Size:
124.68 KB
patch
obsolete
> * Package: dev-db/libdbi-drivers-0.9.0-r1:0 > * Repository: gentoo > * Maintainer: robbat2@gentoo.org > * USE: abi_x86_64 amd64 doc elibc_glibc firebird kernel_linux sqlite > * FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox > >>>> Unpacking source... >>>> Unpacking libdbi-drivers-0.9.0.tar.gz to /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work >>>> Source unpacked in /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work >>>> Preparing source in /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0 ... > * Applying libdbi-drivers-0.9.0-doc-build-fix.patch ... > [ ok ] > * Applying libdbi-drivers-0.9.0-slibtool-libdir.patch ... > [ ok ] > * Running eautoreconf in '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' ... > * Running 'libtoolize --install --copy --force --automake' ... > [ ok ] > * Running 'aclocal -I m4 --system-acdir=/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/temp/aclocal' ... > [ ok ] > * This package has a configure.in file which has long been deprecated. Please > * update it to use configure.ac instead as newer versions of autotools will die > * when it finds this file. See https://bugs.gentoo.org/426262 for details. > * Running 'autoconf --force' ... > [ ok ] > * Running 'autoheader' ... > [ ok ] > * Running 'automake --add-missing --copy --force-missing' ... > [ ok ] > * Running elibtoolize in: libdbi-drivers-0.9.0/ > * Applying portage/1.2.0 patch ... > * Applying sed/1.5.6 patch ... > * Applying as-needed/2.4.3 patch ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0 ... > * econf: updating libdbi-drivers-0.9.0/config.sub with /usr/share/gnuconfig/config.sub > * econf: updating libdbi-drivers-0.9.0/config.guess with /usr/share/gnuconfig/config.guess >./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/libdbi-drivers-0.9.0-r1 --htmldir=/usr/share/doc/libdbi-drivers-0.9.0-r1/html --with-sysroot=/ --libdir=/usr/lib64 --enable-docs --disable-static --with-dbi-libdir=/usr/lib64 --with-sqlite3 --with-firebird >configure: loading site script /usr/share/config.site >checking whether to enable maintainer-specific portions of Makefiles... no >checking for a BSD-compatible install... /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c >checking whether build environment is sane... yes >checking for a race-free mkdir -p... /usr/bin/mkdir -p >checking for gawk... gawk >checking whether make sets $(MAKE)... yes >checking whether make supports nested variables... yes >checking build system type... x86_64-pc-linux-gnu >checking host system type... x86_64-pc-linux-gnu >checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc >checking whether the C compiler works... yes >checking for C compiler default output file name... a.out >checking for suffix of executables... >checking whether we are cross compiling... no >checking for suffix of object files... o >checking whether the compiler supports GNU C... yes >checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes >checking for x86_64-pc-linux-gnu-gcc option to enable C11 features... none needed >checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes >checking whether make supports the include directive... yes (GNU style) >checking dependency style of x86_64-pc-linux-gnu-gcc... none >checking for a sed that does not truncate output... /usr/bin/sed >checking for grep that handles long lines and -e... /usr/bin/grep >checking for egrep... /usr/bin/grep -E >checking for fgrep... /usr/bin/grep -F >checking how to print strings... printf >checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld >checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes >checking for BSD- or MS-compatible name lister (nm)... /usr/bin/x86_64-pc-linux-gnu-nm -B >checking the name lister (/usr/bin/x86_64-pc-linux-gnu-nm -B) interface... BSD nm >checking whether ln -s works... yes >checking the maximum length of command line arguments... 1572864 >checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop >checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop >checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r >checking for x86_64-pc-linux-gnu-file... no >checking for file... file >checking for x86_64-pc-linux-gnu-objdump... objdump >checking how to recognize dependent libraries... pass_all >checking for x86_64-pc-linux-gnu-dlltool... dlltool >checking how to associate runtime and link libraries... printf %s\n >checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar >checking for archiver @FILE support... @ >checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip >checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib >checking command to parse /usr/bin/x86_64-pc-linux-gnu-nm -B output from x86_64-pc-linux-gnu-gcc object... ok >checking for sysroot... / >checking for a working dd... /usr/bin/dd >checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >checking for x86_64-pc-linux-gnu-mt... no >checking for mt... mt >checking if mt is a manifest tool... no >checking for stdio.h... yes >checking for stdlib.h... yes >checking for string.h... yes >checking for inttypes.h... yes >checking for stdint.h... yes >checking for strings.h... yes >checking for sys/stat.h... yes >checking for sys/types.h... yes >checking for unistd.h... yes >checking for dlfcn.h... yes >checking for objdir... .libs >checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no >checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC >checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes >checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes >checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes >checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes >checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes >checking whether -lc should be explicitly linked in... no >checking dynamic linker characteristics... GNU/Linux ld.so >checking how to hardcode library paths into programs... immediate >checking whether stripping libraries is possible... yes >checking if libtool supports shared libraries... yes >checking whether to build shared libraries... yes >checking whether to build static libraries... no >checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E >checking for libdbi framework... checking for dbi/dbi.h... yes >checking for MySQL support... no >checking for PostgreSQL support... no >checking for SQLite support... no >checking for SQLite3 support... yes >checking for sqlite3.h... yes >checking for library containing sqlite3_exec... -lsqlite3 >checking for Msql support... no >checking for Oracle support... no >checking for Firebird/Interbase support... yes >checking for ibase.h... yes >checking for library containing isc_dsql_fetch... no >checking for isql-fb... no >checking for isql... isql >checking for Freetds support... no >checking for Ingres support... no >checking for IBM DB2 support... no >checking for strtoll... yes >checking for atoll... yes >checking for vasprintf... yes >checking for asprintf... yes >checking for libdbi library... yes: libs in /usr/lib64 >checking for string.h... (cached) yes >checking for strings.h... (cached) yes >checking that generated files are newer than configure... done >configure: creating ./config.status >config.status: creating libdbi-drivers.spec >config.status: creating Makefile >config.status: creating doc/Makefile >config.status: creating doc/include/Makefile >config.status: creating drivers/Makefile >config.status: creating drivers/mysql/Makefile >config.status: creating drivers/pgsql/Makefile >config.status: creating drivers/sqlite/Makefile >config.status: creating drivers/sqlite3/Makefile >config.status: creating drivers/msql/Makefile >config.status: creating drivers/oracle/Makefile >config.status: creating drivers/firebird/Makefile >config.status: creating drivers/freetds/Makefile >config.status: creating drivers/ingres/Makefile >config.status: creating drivers/db2/Makefile >config.status: creating tests/Makefile >config.status: creating tests/cgreen/Makefile >config.status: creating tests/test_dbi.cfg >config.status: creating tests/plugin_settings.sh >config.status: creating config.h >config.status: executing depfiles commands >config.status: executing libtool commands >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0 ... >make -j5 >make all-recursive >make[1]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' >Making all in drivers >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >Making all in mysql >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >Making all in pgsql >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >Making all in sqlite >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >Making all in sqlite3 >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >/bin/sh ../../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/sqlite3\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o dbd_sqlite3.lo dbd_sqlite3.c >libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/sqlite3\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c dbd_sqlite3.c -fPIC -DPIC -o .libs/dbd_sqlite3.o >dbd_sqlite3.c: In function 'dbd_list_dbs': >dbd_sqlite3.c:426:5: warning: 'readdir_r' is deprecated [-Wdeprecated-declarations] > 426 | retval = readdir_r(dp, entry, &result); > | ^~~~~~ >In file included from dbd_sqlite3.c:50: >/usr/include/dirent.h:185:12: note: declared here > 185 | extern int readdir_r (DIR *__restrict __dirp, > | ^~~~~~~~~ >dbd_sqlite3.c:421:3: warning: ignoring return value of 'getcwd' declared with attribute 'warn_unused_result' [-Wunused-result] > 421 | getcwd(old_cwd, _POSIX_PATH_MAX); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c:422:3: warning: ignoring return value of 'chdir' declared with attribute 'warn_unused_result' [-Wunused-result] > 422 | chdir(sq_datadir); > | ^~~~~~~~~~~~~~~~~ >dbd_sqlite3.c:491:3: warning: ignoring return value of 'chdir' declared with attribute 'warn_unused_result' [-Wunused-result] > 491 | chdir(old_cwd); > | ^~~~~~~~~~~~~~ >dbd_sqlite3.c: In function 'dbd_list_tables': >dbd_sqlite3.c:537:5: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 537 | asprintf(&sql_cmd, "SELECT name FROM sqlite_master WHERE type='table' ORDER BY name"); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c:540:5: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 540 | asprintf(&sql_cmd, "SELECT name FROM sqlite_master WHERE type='table' AND name LIKE '%s' ORDER BY name", pattern); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c:547:7: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 547 | asprintf(&sql_cmd, "INSERT INTO libdbi_tablenames VALUES ('%s')", dbi_result_get_string(dbi_result, "name")); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c: In function 'dbd_savepoint': >dbd_sqlite3.c:757:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 757 | asprintf(&query, "SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c: In function 'dbd_rollback_to_savepoint': >dbd_sqlite3.c:776:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 776 | asprintf(&query, "ROLLBACK TO SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_sqlite3.c: In function 'dbd_release_savepoint': >dbd_sqlite3.c:795:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 795 | asprintf(&query, "RELEASE SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >/bin/sh ../../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -module -avoid-version -lsqlite3 -no-undefined -ldbi -L/usr/lib64 -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 -o libdbdsqlite3.la -rpath /usr/lib64/dbd dbd_sqlite3.lo >libtool: link: x86_64-pc-linux-gnu-gcc -shared -fPIC -DPIC .libs/dbd_sqlite3.o -lsqlite3 -ldbi -L/usr/lib64 -Wl,--as-needed -O2 -march=native -Wl,-O1 -Wl,--defsym=__gentoo_check_ldflags__=0 -Wl,-soname -Wl,libdbdsqlite3.so -o .libs/libdbdsqlite3.so >libtool: link: ( cd ".libs" && rm -f "libdbdsqlite3.la" && ln -s "../libdbdsqlite3.la" "libdbdsqlite3.la" ) >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >Making all in msql >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >Making all in oracle >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >Making all in firebird >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >/bin/sh ../../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/firebird\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o dbd_firebird.lo dbd_firebird.c >/bin/sh ../../libtool --tag=CC --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/firebird\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o utility.lo utility.c >Converting dbd_firebird.sgml to HTML... >mkdir -p dbd_firebird && cd dbd_firebird && openjade -t sgml -d ../../../doc/include/doc-html.dsl ../dbd_firebird.sgml >libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/firebird\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c utility.c -fPIC -DPIC -o .libs/utility.o >libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -DDBDIR=\"/var/lib/lib/libdbi/firebird\" -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c dbd_firebird.c -fPIC -DPIC -o .libs/dbd_firebird.o >dbd_firebird.c: In function 'dbd_get_engine_version': >dbd_firebird.c:249:41: warning: implicit declaration of function 'isdigit' [-Wimplicit-function-declaration] > 249 | while (start>version && isdigit((int)(*(start-1)))) { > | ^~~~~~~ >dbd_firebird.c:50:1: note: include '<ctype.h>' or provide a declaration of 'isdigit' > 49 | #include "utility.h" > +++ |+#include <ctype.h> > 50 | >utility.c: In function '_dbd_real_connect': >utility.c:102:17: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 102 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >In file included from utility.c:16: >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >utility.c: In function '_get_row_data': >utility.c:234:39: warning: initialization of 'isc_blob_handle' {aka 'unsigned int'} from 'void *' makes integer from pointer without a cast [-Wint-conversion] > 234 | isc_blob_handle blob_handle = NULL; /* Blob handle. */ > | ^~~~ >dbd_firebird.c: In function 'dbd_query': >dbd_firebird.c:357:32: warning: initialization of 'isc_stmt_handle' {aka 'unsigned int'} from 'void *' makes integer from pointer without a cast [-Wint-conversion] > 357 | isc_stmt_handle stmt = NULL; /* statement handle */ > | ^~~~ >dbd_firebird.c:375:24: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 375 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >In file included from dbd_firebird.c:45: >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >dbd_firebird.c:389:24: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 389 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >dbd_firebird.c:409:32: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 409 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >dbd_firebird.c:423:40: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 423 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >dbd_firebird.c:466:40: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 466 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >dbd_firebird.c:499:32: warning: 'isc_interprete' is deprecated [-Wdeprecated-declarations] > 499 | isc_interprete(msg, &pvector); > | ^~~~~~~~~~~~~~ >/usr/include/ibase.h:824:39: note: declared here > 824 | ISC_LONG FB_API_DEPRECATED ISC_EXPORT isc_interprete(ISC_SCHAR*, > | ^~~~~~~~~~~~~~ >utility.c: In function 'return_generator_value': >utility.c:396:9: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 396 | asprintf(&sql_cmd, "SELECT GEN_ID( %s ,%d ) FROM RDB$DATABASE",sequence, type ); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_firebird.c: In function 'dbd_list_tables': >dbd_firebird.c:284:17: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 284 | asprintf(&sql_cmd, "SELECT RDB$RELATION_NAME FROM RDB$RELATIONS WHERE RDB$SYSTEM_FLAG = 0 " > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 285 | " AND RDB$RELATION_NAME LIKE '%s'", pattern); > | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_firebird.c: In function 'dbd_savepoint': >dbd_firebird.c:558:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 558 | asprintf(&query, "SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_firebird.c: In function 'dbd_rollback_to_savepoint': >dbd_firebird.c:577:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 577 | asprintf(&query, "ROLLBACK TO SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >dbd_firebird.c: In function 'dbd_release_savepoint': >dbd_firebird.c:596:3: warning: ignoring return value of 'asprintf' declared with attribute 'warn_unused_result' [-Wunused-result] > 596 | asprintf(&query, "RELEASE SAVEPOINT %s", savepoint); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >/bin/sh ../../libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -module -avoid-version -no-undefined -ldbi -L/usr/lib64 -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 -o libdbdfirebird.la -rpath /usr/lib64/dbd dbd_firebird.lo utility.lo >libtool: link: x86_64-pc-linux-gnu-gcc -shared -fPIC -DPIC .libs/dbd_firebird.o .libs/utility.o -ldbi -L/usr/lib64 -Wl,--as-needed -O2 -march=native -Wl,-O1 -Wl,--defsym=__gentoo_check_ldflags__=0 -Wl,-soname -Wl,libdbdfirebird.so -o .libs/libdbdfirebird.so >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:11:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:13:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:14:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:18:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:19:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:22:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:23:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:29:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:34:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:39:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:44:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:46:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:52:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:53:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:76:2:E: entity end not allowed in processing instruction >openjade:../../../doc/include/doc-html.dsl:3:0:E: DTD did not contain element declaration for document type name >openjade:../../../doc/include/doc-html.dsl:2:0:E: notation "dsssl" for entity "docbook.dsl" undefined >openjade:../../../doc/include/doc-html.dsl:5:12:E: element "style-sheet" undefined >openjade:../../../doc/include/doc-html.dsl:6:25:E: there is no attribute "use" >openjade:../../../doc/include/doc-html.dsl:6:34:E: element "style-specification" undefined >openjade:../../../doc/include/doc-html.dsl:7:25:E: element "style-specification-body" undefined >openjade:../../../doc/include/doc-html.dsl:220:27:E: there is no attribute "id" >openjade:../../../doc/include/doc-html.dsl:220:46:E: there is no attribute "document" >openjade:../../../doc/include/doc-html.dsl:220:59:E: element "external-specification" undefined >openjade:../../../doc/include/doc-html.dsl:222:13:E: end tag for "external-specification" omitted, but OMITTAG NO was specified >openjade:../../../doc/include/doc-html.dsl:220:0: start tag was here >openjade:E: specification document does not have the DSSSL architecture as a base architecture >firebird driver manualA libdbi driver providing connectivity to Firebird and Interbase databases.ChristianStamgrenchristian@stamgren.comMarkusHoenickamhoenicka@users.sourceforge.net Permission is granted to copy, distribute and/or modify this > document under the terms of the GNU Free Documentation License, > Version 1.1 or any later version published by the Free Software > Foundation; with no Invariant Sections, with no Front-Cover Texts, > and with no Back-Cover Texts. A copy of the license is included in > . > 0.12008-01-02Prefacelibdbi is a database abstraction layer written in C. It implements a framework that can utilize separate driver libraries for specific database servers. The libdbi-drivers project provides the drivers necessary to talk to the supported database servers.This manual provides information about the Firebird/Interbase driver. The manual is intended for programmers who write applications linked against libdbi and who want their applications to work with Firebird or Interbase database engines.Questions and comments about the Firebird/Interbase driver should be sent to the libdbi-drivers-devel mailing list. Visit the libdbi-drivers-devel list page to subscribe and for further information. Questions and comments about the libdbi library should be sent to the appropriate libdbi mailing list.The Firebird/Interbase driver was developed by Christian Stamgren.IntroductionFirebird is the free cousin of the InterBase SQL database engine, which has a long and winding history related to the repeated reinventions of the Borland, then Inprise, then Borland/Inprise, then again Borland company. Although the internal name of the driver is "firebird", it is supposed to work with the InterBase products as well.InstallationThis chapter describes the prerequisites and the procedures to build and install the firebird driver from the sources.PrerequisitesThe following packages have to be installed on your system:libdbiThis library provides the framework of the database abstraction layer which can utilize the firebird driver to perform database operations. The download page as well as the mailing lists with bug reports and patches are accessible at sourceforge.net/projects/libdbi. The current version of the firebird driver requires libdbi version 0.8.x.libfbembedThis library implements the client API for Firebird/InterBase databases which provides access both locally and through the network. Find the most recent release at www.firebirdsql.org. The current version of the firebird driver was tested with Firebird versions 1.5.3 and 2.0.3 and should work with all recent releases.Build and install the firebird driverFirst you have to unpack the libdbi-drivers archive in a suitable directory. Unpacking will create a new subdirectory libdbi-drivers-X.Y where "X.Y" denotes the version:$ tar -xzf libdbi-drivers-X.Y.tar.gzThe libdbi-drivers project consists of several drivers that use a common build system. Therefore you must tell configure explicitly that you want to build the firebird driver (you can list as many drivers as you want to build):$ cd libdbi-drivers$ ./configure --with-firebirdRun ./configure --help to find out about additional options.Then build the driver with the command:$ makeIf the command results in error messages about the Makefile syntax, you may have to explicitly invoke gmake, the GNU version of make, on your system.Then install the driver with the command (you'll need root permissions to do this):$ make installTo test the operation of the newly installed driver, use the command:$ make checkThis command creates and runs a test program that performs a few basic input and output tests. The program will ask for an administrator username and password. Default Firebird installations usually call the database superuser "sysdba" so this user is always a good start. Be sure to provide the name of a database which does not already exist (avoid 'test' which is used on many systems). To keep file permission problems out of this test (more on this below), you may prefer to keep the hostname empty and to specify a directory with write access.If for some reason you need to re-create the autoconf/automake-related files, try running ./autogen.sh.Driver optionsYour application has to initialize libdbi drivers by setting some driver options with the dbi_conn_set_option() and the dbi_conn_set_option_numeric() library functions. The firebird driver supports the following general options:hostThe hostname or IP address of the Firebird database server. Use "localhost" or the real hostname of your local computer to connect to a Firebird server running on the local machine through the network (this is the only way to connect to a local super-server). Do not set the host option if you want to work with a local database, without going through a server.usernameThe name of the user accessing the database.passwordThe password of the user accessing the database.dbnameThe name of the database used for the initial connection. If your program must be able to connect to a fresh Firebird installation, use the test database libdbitest created by make check.encodingThe IANA name of a character encoding which is to be used as the connection encoding. Input and output data will be silently converted from and to this character encoding, respectively. If you set this option to "auto", the connection encoding will be the same as the default encoding of the database.In addition, the following firebird-specific options are supported:firebird_dbdirThis is the directory that holds the Firebird database files. Depending on the settings of the host option, this may refer to a directory on a local or on a remote machine. The ownership and the permissions must match the mode of access. If you create or access a file locally (i.e. with host not set), the account you're logged in needs write and execute permissions. If you set the host, the account your server runs in must have write and execute permissions. This is true even if you connect to your own machine via localhost. Default server installations use the "firebird" account. The database directory should then be owned by firebird:firebird with write and execute permissions for both the user and the group. It should then be sufficient to add yourself to the firebird group to gain access to the database directory.If this option is not specified, a compile-time default directory will be used. Needless to say, this is going to work only if you work on localhost. By default, this directory (usually /usr/local/var/lib/libdbi/firebird) has read and write permissions for everyone with the sticky bit set. If this is not suitable for your application, use a custom directory with your preferred permissions instead.Peculiarities you should know aboutThis chapter lists known peculiarities of the firebird driver. This includes Firebird features that differ from what you know from the other database servers supported by libdbi, and it includes features and misfeatures introduced by the firebird driver. It is the intention of the libdbi developers to reduce the number of misfeatures in future releases if possible.Firebird (mis)featuresTo determine the number of matches, all results have to be retrieved first. This is very inefficient and may provide a bottleneck for large applications.DATETIME and TIME do not appear to support timezoneschar, unsigned char, long long, and unsigned long long types are not supported.GNU Free Documentation LicenseVersion 1.1, March 2000Copyright (C) 2000 Free Software Foundation, Inc. >59 Temple Place, Suite 330, Boston, MA 02111-1307 USA >Everyone is permitted to copy and distribute verbatim copies >of this license document, but changing it is not allowed.0. PREAMBLEThe purpose of this License is to make a manual, textbook, > or other written document "free" in the sense of freedom: to > assure everyone the effective freedom to copy and redistribute it, > with or without modifying it, either commercially or > noncommercially. Secondarily, this License preserves for the > author and publisher a way to get credit for their work, while not > being considered responsible for modifications made by > others.This License is a kind of "copyleft", which means that > derivative works of the document must themselves be free in the > same sense. It complements the GNU General Public License, which > is a copyleft license designed for free software.We have designed this License in order to use it for manuals > for free software, because free software needs free documentation: > a free program should come with manuals providing the same > freedoms that the software does. But this License is not limited > to software manuals; it can be used for any textual work, > regardless of subject matter or whether it is published as a > printed book. We recommend this License principally for works > whose purpose is instruction or reference.1. APPLICABILITY AND DEFINITIONSThis License applies to any manual or other work that > contains a notice placed by the copyright holder saying it can be > distributed under the terms of this License. The "Document", > below, refers to any such manual or work. Any member of the > public is a licensee, and is addressed as "you".A "Modified Version" of the Document means any work > containing the Document or a portion of it, either copied > verbatim, or with modifications and/or translated into another > language.A "Secondary Section" is a named appendix or a front-matter > section of the Document that deals exclusively with the > relationship of the publishers or authors of the Document to the > Document's overall subject (or to related matters) and contains > nothing that could fall directly within that overall subject. > (For example, if the Document is in part a textbook of > mathematics, a Secondary Section may not explain any mathematics.) > The relationship could be a matter of historical connection with > the subject or with related matters, or of legal, commercial, > philosophical, ethical or political position regarding > them.The "Invariant Sections" are certain Secondary Sections > whose titles are designated, as being those of Invariant Sections, > in the notice that says that the Document is released under this > License.The "Cover Texts" are certain short passages of text that > are listed, as Front-Cover Texts or Back-Cover Texts, in the > notice that says that the Document is released under this > License.A "Transparent" copy of the Document means a > machine-readable copy, represented in a format whose specification > is available to the general public, whose contents can be viewed > and edited directly and straightforwardly with generic text > editors or (for images composed of pixels) generic paint programs > or (for drawings) some widely available drawing editor, and that > is suitable for input to text formatters or for automatic > translation to a variety of formats suitable for input to text > formatters. A copy made in an otherwise Transparent file format > whose markup has been designed to thwart or discourage subsequent > modification by readers is not Transparent. A copy that is not > "Transparent" is called "Opaque".Examples of suitable formats for Transparent copies include > plain ASCII without markup, Texinfo input format, LaTeX input > format, SGML or XML using a publicly available DTD, and > standard-conforming simple HTML designed for human modification. > Opaque formats include PostScript, PDF, proprietary formats that > can be read and edited only by proprietary word processors, SGML > or XML for which the DTD and/or processing tools are not generally > available, and the machine-generated HTML produced by some word > processors for output purposes only.The "Title Page" means, for a printed book, the title page > itself, plus such following pages as are needed to hold, legibly, > the material this License requires to appear in the title page. > For works in formats which do not have any title page as such, > "Title Page" means the text near the most prominent appearance of > the work's title, preceding the beginning of the body of the > text.2. VERBATIM COPYINGYou may copy and distribute the Document in any medium, > either commercially or noncommercially, provided that this > License, the copyright notices, and the license notice saying this > License applies to the Document are reproduced in all copies, and > that you add no other conditions whatsoever to those of this > License. You may not use technical measures to obstruct or > control the reading or further copying of the copies you make or > distribute. However, you may accept compensation in exchange for > copies. If you distribute a large enough number of copies you > must also follow the conditions in section 3.You may also lend copies, under the same conditions stated > above, and you may publicly display copies.3. COPYING IN QUANTITYIf you publish printed copies of the Document numbering more > than 100, and the Document's license notice requires Cover Texts, > you must enclose the copies in covers that carry, clearly and > legibly, all these Cover Texts: Front-Cover Texts on the front > cover, and Back-Cover Texts on the back cover. Both covers must > also clearly and legibly identify you as the publisher of these > copies. The front cover must present the full title with all > words of the title equally prominent and visible. You may add > other material on the covers in addition. Copying with changes > limited to the covers, as long as they preserve the title of the > Document and satisfy these conditions, can be treated as verbatim > copying in other respects.If the required texts for either cover are too voluminous to > fit legibly, you should put the first ones listed (as many as fit > reasonably) on the actual cover, and continue the rest onto > adjacent pages.If you publish or distribute Opaque copies of the Document > numbering more than 100, you must either include a > machine-readable Transparent copy along with each Opaque copy, or > state in or with each Opaque copy a publicly-accessible > computer-network location containing a complete Transparent copy > of the Document, free of added material, which the general > network-using public has access to download anonymously at no > charge using public-standard network protocols. If you use the > latter option, you must take reasonably prudent steps, when you > begin distribution of Opaque copies in quantity, to ensure that > this Transparent copy will remain thus accessible at the stated > location until at least one year after the last time you > distribute an Opaque copy (directly or through your agents or > retailers) of that edition to the public.It is requested, but not required, that you contact the > authors of the Document well before redistributing any large > number of copies, to give them a chance to provide you with an > updated version of the Document.4. MODIFICATIONSYou may copy and distribute a Modified Version of the > Document under the conditions of sections 2 and 3 above, provided > that you release the Modified Version under precisely this > License, with the Modified Version filling the role of the > Document, thus licensing distribution and modification of the > Modified Version to whoever possesses a copy of it. In addition, > you must do these things in the Modified Version:Use in the Title Page > (and on the covers, if any) a title distinct from that of the > Document, and from those of previous versions (which should, if > there were any, be listed in the History section of the > Document). You may use the same title as a previous version if > the original publisher of that version gives permission.List on the Title Page, > as authors, one or more persons or entities responsible for > authorship of the modifications in the Modified Version, > together with at least five of the principal authors of the > Document (all of its principal authors, if it has less than > five).State on the Title page > the name of the publisher of the Modified Version, as the > publlibtool: link: ( cd ".libs" && rm -f "libdbdfirebird.la" && ln -s "../libdbdfirebird.la" "libdbdfirebird.la" ) >isher.Preserve all the > copyright notices of the Document.Add an appropriate > copyright notice for your modifications adjacent to the other > copyright notices.Include, immediately > after the copyright notices, a license notice giving the public > permission to use the Modified Version under the terms of this > License, in the form shown in the Addendum below.Preserve in that license > notice the full lists of Invariant Sections and required Cover > Texts given in the Document's license notice.Include an unaltered > copy of this License.Preserve the section > entitled "History", and its title, and add to it an item stating > at least the title, year, new authors, and publisher of the > Modified Version as given on the Title Page. If there is no > section entitled "History" in the Document, create one stating > the title, year, authors, and publisher of the Document as given > on its Title Page, then add an item describing the Modified > Version as stated in the previous sentence.Preserve the network > location, if any, given in the Document for public access to a > Transparent copy of the Document, and likewise the network > locations given in the Document for previous versions it was > based on. These may be placed in the "History" section. You > may omit a network location for a work that was published at > least four years before the Document itself, or if the original > publisher of the version it refers to gives permission.In any section entitled > "Acknowledgements" or "Dedications", preserve the section's > title, and preserve in the section all the substance and tone of > each of the contributor acknowledgements and/or dedications > given therein.Preserve all the > Invariant Sections of the Document, unaltered in their text and > in their titles. Section numbers or the equivalent are not > considered part of the section titles.Delete any section > entitled "Endorsements". Such a section may not be included in > the Modified Version.Do not retitle any > existing section as "Endorsements" or to conflict in title with > any Invariant Section.If the Modified Version includes new front-matter sections > or appendices that qualify as Secondary Sections and contain no > material copied from the Document, you may at your option > designate some or all of these sections as invariant. To do this, > add their titles to the list of Invariant Sections in the Modified > Version's license notice. These titles must be distinct from any > other section titles.You may add a section entitled "Endorsements", provided it > contains nothing but endorsements of your Modified Version by > various parties--for example, statements of peer review or that > the text has been approved by an organization as the authoritative > definition of a standard.You may add a passage of up to five words as a Front-Cover > Text, and a passage of up to 25 words as a Back-Cover Text, to the > end of the list of Cover Texts in the Modified Version. Only one > passage of Front-Cover Text and one of Back-Cover Text may be > added by (or through arrangements made by) any one entity. If the > Document already includes a cover text for the same cover, > previously added by you or by arrangement made by the same entity > you are acting on behalf of, you may not add another; but you may > replace the old one, on explicit permission from the previous > publisher that added the old one.The author(s) and publisher(s) of the Document do not by > this License give permission to use their names for publicity for > or to assert or imply endorsement of any Modified Version.5. COMBINING DOCUMENTSYou may combine the Document with other documents released > under this License, under the terms defined in section 4 above for > modified versions, provided that you include in the combination > all of the Invariant Sections of all of the original documents, > unmodified, and list them all as Invariant Sections of your > combined work in its license notice.The combined work need only contain one copy of this > License, and multiple identical Invariant Sections may be replaced > with a single copy. If there are multiple Invariant Sections with > the same name but different contents, make the title of each such > section unique by adding at the end of it, in parentheses, the > name of the original author or publisher of that section if known, > or else a unique number. Make the same adjustment to the section > titles in the list of Invariant Sections in the license notice of > the combined work.In the combination, you must combine any sections entitled > "History" in the various original documents, forming one section > entitled "History"; likewise combine any sections entitled > "Acknowledgements", and any sections entitled "Dedications". You > must delete all sections entitled "Endorsements."6. COLLECTIONS OF DOCUMENTSYou may make a collection consisting of the Document and > other documents released under this License, and replace the > individual copies of this License in the various documents with a > single copy that is included in the collection, provided that you > follow the rules of this License for verbatim copying of each of > the documents in all other respects.You may extract a single document from such a collection, > and distribute it individually under this License, provided you > insert a copy of this License into the extracted document, and > follow this License in all other respects regarding verbatim > copying of that document.7. AGGREGATION WITH INDEPENDENT WORKSA compilation of the Document or its derivatives with other > separate and independent documents or works, in or on a volume of > a storage or distribution medium, does not as a whole count as a > Modified Version of the Document, provided no compilation > copyright is claimed for the compilation. Such a compilation is > called an "aggregate", and this License does not apply to the > other self-contained works thus compiled with the Document, on > account of their being thus compiled, if they are not themselves > derivative works of the Document.If the Cover Text requirement of section 3 is applicable to > these copies of the Document, then if the Document is less than > one quarter of the entire aggregate, the Document's Cover Texts > may be placed on covers that surround only the Document within the > aggregate. Otherwise they must appear on covers around the whole > aggregate.8. TRANSLATIONTranslation is considered a kind of modification, so you may > distribute translations of the Document under the terms of section > 4. Replacing Invariant Sections with translations requires > special permission from their copyright holders, but you may > include translations of some or all Invariant Sections in addition > to the original versions of these Invariant Sections. You may > include a translation of this License provided that you also > include the original English version of this License. In case of > a disagreement between the translation and the original English > version of this License, the original English version will > prevail.9. TERMINATIONYou may not copy, modify, sublicense, or distribute the > Document except as expressly provided for under this License. Any > other attempt to copy, modify, sublicense or distribute the > Document is void, and will automatically terminate your rights > under this License. However, parties who have received copies, or > rights, from you under this License will not have their licenses > terminated so long as such parties remain in full > compliance.10. FUTURE REVISIONS OF THIS LICENSEThe Free Software Foundation may publish new, revised > versions of the GNU Free Documentation License from time to time. > Such new versions will be similar in spirit to the present > version, but may differ in detail to address new problems or > concerns. See http://www.gnu.org/copyleft/.Each version of the License is given a distinguishing > version number. If the Document specifies that a particular > numbered version of this License "or any later version" applies to > it, you have the option of following the terms and conditions > either of that specified version or of any later version that has > been published (not as a draft) by the Free Software Foundation. > If the Document does not specify a version number of this License, > you may choose any version ever published (not as a draft) by the > Free Software Foundation.How to use this License for your documentsTo use this License in a document you have written, include > a copy of the License in the document and put the following > copyright and license notices just after the title page: Copyright (c) YEAR YOUR NAME. > Permission is granted to copy, distribute and/or modify this document > under the terms of the GNU Free Documentation License, Version 1.1 > or any later version published by the Free Software Foundation; > with the Invariant Sections being LIST THEIR TITLES, with the > Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. > A copy of the license is included in the section entitled "GNU > Free Documentation License".If you have no Invariant Sections, write "with no Invariant > Sections" instead of saying which ones are invariant. If you have > no Front-Cover Texts, write "no Front-Cover Texts" instead of > "Front-Cover Texts being LIST"; likewise for Back-Cover > Texts.If your document contains nontrivial examples of program > code, we recommend releasing these examples in parallel under your > choice of free software license, such as the GNU General Public > License, to permit their use in free software.make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >Making all in freetds >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/freetds' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/freetds' >Making all in ingres >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/ingres' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/ingres' >Making all in db2 >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/db2' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/db2' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >make[3]: Nothing to be done for 'all-am'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >Making all in tests >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests' >Making all in cgreen >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests/cgreen' >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o unit.o `test -f 'src/unit.c' || echo './'`src/unit.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o messaging.o `test -f 'src/messaging.c' || echo './'`src/messaging.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o breadcrumb.o `test -f 'src/breadcrumb.c' || echo './'`src/breadcrumb.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o reporter.o `test -f 'src/reporter.c' || echo './'`src/reporter.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o assertions.o `test -f 'src/assertions.c' || echo './'`src/assertions.c >src/messaging.c: In function âstart_cgreen_messagingâ: >src/messaging.c:40:5: warning: ignoring return value of âpipeâ declared with attribute âwarn_unused_resultâ [-Wunused-result] > 40 | pipe(pipes); > | ^~~~~~~~~~~ >src/messaging.c: In function âsend_cgreen_messageâ: >src/messaging.c:56:5: warning: ignoring return value of âwriteâ declared with attribute âwarn_unused_resultâ [-Wunused-result] > 56 | write(queues[messaging].writepipe, message, sizeof(CgreenMessage)); > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >src/unit.c: In function âwait_for_child_processâ: >src/unit.c:229:5: warning: implicit declaration of function âwaitâ; did you mean âwantâ? [-Wimplicit-function-declaration] > 229 | wait(&status); > | ^~~~ > | want >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o vector.o `test -f 'src/vector.c' || echo './'`src/vector.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o mocks.o `test -f 'src/mocks.c' || echo './'`src/mocks.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o constraint.o `test -f 'src/constraint.c' || echo './'`src/constraint.c >src/constraint.c: In function âwith_â: >src/constraint.c:104:22: warning: assignment to âvoid (*)(Constraint *, const char *, intptr_t, const char *, int, TestReporter *)â {aka âvoid (*)(struct Constraint_ *, const char *, long int, const char *, int, struct TestReporter_ *)â} from incompatible pointer type âvoid (*)(Constraint *, const char *, const char *, intptr_t, const char *, int, TestReporter *)â {aka âvoid (*)(struct Constraint_ *, const char *, const char *, long int, const char *, int, struct TestReporter_ *)â} [-Wincompatible-pointer-types] > 104 | constraint->test = &test_with_matcher; > | ^ >src/constraint.c: In function âcompare_using_matcherâ: >src/constraint.c:167:39: warning: initialization of âint (*)(const void *)â from âintptr_tâ {aka âlong intâ} makes pointer from integer without a cast [-Wint-conversion] > 167 | int (*matches)(const void*) = constraint->expected; > | ^~~~~~~~~~ >src/constraint.c:168:20: warning: passing argument 1 of âmatchesâ makes pointer from integer without a cast [-Wint-conversion] > 168 | return matches(actual); > | ^~~~~~ > | | > | intptr_t {aka long int} >src/constraint.c:168:20: note: expected âconst void *â but argument is of type âintptr_tâ {aka âlong intâ} >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o parameters.o `test -f 'src/parameters.c' || echo './'`src/parameters.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o text_reporter.o `test -f 'src/text_reporter.c' || echo './'`src/text_reporter.c >x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -Iinclude -std=gnu99 -O2 -pipe -march=native -fno-diagnostics-color -falign-functions=32:25:16 -c -o cdash_reporter.o `test -f 'src/cdash_reporter.c' || echo './'`src/cdash_reporter.c >rm -f libcgreen.a >x86_64-pc-linux-gnu-ar cru libcgreen.a unit.o messaging.o breadcrumb.o reporter.o assertions.o vector.o mocks.o constraint.o parameters.o text_reporter.o cdash_reporter.o >x86_64-pc-linux-gnu-ranlib libcgreen.a >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests/cgreen' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests' >make[3]: Nothing to be done for 'all-am'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/tests' >Making all in doc >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc' >Making all in include >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc/include' >make[3]: Nothing to be done for 'all'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc/include' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc' >make[3]: Nothing to be done for 'all-am'. >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/doc' >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' >make[1]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' >>>> Source compiled. >>>> Test phase [not enabled]: dev-db/libdbi-drivers-0.9.0-r1 > >>>> Install dev-db/libdbi-drivers-0.9.0-r1 into /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image >make -j5 DESTDIR=/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image install >Making install in drivers >make[1]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >Making install in mysql >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/mysql' >Making install in pgsql >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/pgsql' >Making install in sqlite >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >/bin/sh /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/install-sh -d /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/sqlite >chmod 1777 /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/sqlite >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite' >Making install in sqlite3 >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >/bin/sh /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/install-sh -d /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/sqlite3 > /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0/dbd_sqlite3' > /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0' > /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd' > /bin/sh ../../libtool --mode=install /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c libdbdsqlite3.la '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd' > /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 dbd_sqlite3/c134.html dbd_sqlite3/c34.html dbd_sqlite3/c47.html dbd_sqlite3/c98.html dbd_sqlite3/copying-fdl.html dbd_sqlite3/f23.html dbd_sqlite3/index.html dbd_sqlite3/x137.html dbd_sqlite3/x209.html dbd_sqlite3/x50.html dbd_sqlite3/x64.html '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0/dbd_sqlite3' > /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 dbd_sqlite3.pdf '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0' >chmod 1777 /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/sqlite3 >libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libdbdsqlite3.so /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd/libdbdsqlite3.so >libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libdbdsqlite3.lai /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd/libdbdsqlite3.la >libtool: warning: remember to run 'libtool --finish /usr/lib64/dbd' >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/sqlite3' >Making install in msql >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/msql' >Making install in oracle >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/oracle' >Making install in firebird >make[2]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >Converting dbd_firebird.sgml to HTML... >mkdir -p dbd_firebird && cd dbd_firebird && openjade -t sgml -d ../../../doc/include/doc-html.dsl ../dbd_firebird.sgml >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:11:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:13:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:14:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:18:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:19:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:22:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:23:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:29:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:34:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:39:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:44:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:46:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:52:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:53:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:76:2:E: entity end not allowed in processing instruction >openjade:../../../doc/include/doc-html.dsl:3:0:E: DTD did not contain element declaration for document type name >openjade:../../../doc/include/doc-html.dsl:2:0:E: notation "dsssl" for entity "docbook.dsl" undefined >openjade:../../../doc/include/doc-html.dsl:5:12:E: element "style-sheet" undefined >openjade:../../../doc/include/doc-html.dsl:6:25:E: there is no attribute "use" >openjade:../../../doc/include/doc-html.dsl:6:34:E: element "style-specification" undefined >openjade:../../../doc/include/doc-html.dsl:7:25:E: element "style-specification-body" undefined >openjade:../../../doc/include/doc-html.dsl:220:27:E: there is no attribute "id" >openjade:../../../doc/include/doc-html.dsl:220:46:E: there is no attribute "document" >openjade:../../../doc/include/doc-html.dsl:220:59:E: element "external-specification" undefined >openjade:../../../doc/include/doc-html.dsl:222:13:E: end tag for "external-specification" omitted, but OMITTAG NO was specified >openjade:../../../doc/include/doc-html.dsl:220:0: start tag was here >openjade:E: specification document does not have the DSSSL architecture as a base architecture >firebird driver manualA libdbi driver providing connectivity to Firebird and Interbase databases.ChristianStamgrenchristian@stamgren.comMarkusHoenickamhoenicka@users.sourceforge.net Permission is granted to copy, distribute and/or modify this > document under the terms of the GNU Free Documentation License, > Version 1.1 or any later version published by the Free Software > Foundation; with no Invariant Sections, with no Front-Cover Texts, > and with no Back-Cover Texts. A copy of the license is included in > . > 0.12008-01-02Prefacelibdbi is a database abstraction layer written in C. It implements a framework that can utilize separate driver libraries for specific database servers. The libdbi-drivers project provides the drivers necessary to talk to the supported database servers.This manual provides information about the Firebird/Interbase driver. The manual is intended for programmers who write applications linked against libdbi and who want their applications to work with Firebird or Interbase database engines.Questions and comments about the Firebird/Interbase driver should be sent to the libdbi-drivers-devel mailing list. Visit the libdbi-drivers-devel list page to subscribe and for further information. Questions and comments about the libdbi library should be sent to the appropriate libdbi mailing list.The Firebird/Interbase driver was developed by Christian Stamgren.IntroductionFirebird is the free cousin of the InterBase SQL database engine, which has a long and winding history related to the repeated reinventions of the Borland, then Inprise, then Borland/Inprise, then again Borland company. Although the internal name of the driver is "firebird", it is supposed to work with the InterBase products as well.InstallationThis chapter describes the prerequisites and the procedures to build and install the firebird driver from the sources.PrerequisitesThe following packages have to be installed on your system:libdbiThis library provides the framework of the database abstraction layer which can utilize the firebird driver to perform database operations. The download page as well as the mailing lists with bug reports and patches are accessible at sourceforge.net/projects/libdbi. The current version of the firebird driver requires libdbi version 0.8.x.libfbembedThis library implements the client API for Firebird/InterBase databases which provides access both locally and through the network. Find the most recent release at www.firebirdsql.org. The current version of the firebird driver was tested with Firebird versions 1.5.3 and 2.0.3 and should work with all recent releases.Build and install the firebird driverFirst you have to unpack the libdbi-drivers archive in a suitable directory. Unpacking will create a new subdirectory libdbi-drivers-X.Y where "X.Y" denotes the version:$ tar -xzf libdbi-drivers-X.Y.tar.gzThe libdbi-drivers project consists of several drivers that use a common build system. Therefore you must tell configure explicitly that you want to build the firebird driver (you can list as many drivers as you want to build):$ cd libdbi-drivers$ ./configure --with-firebirdRun ./configure --help to find out about additional options.Then build the driver with the command:$ makeIf the command results in error messages about the Makefile syntax, you may have to explicitly invoke gmake, the GNU version of make, on your system.Then install the driver with the command (you'll need root permissions to do this):$ make installTo test the operation of the newly installed driver, use the command:$ make checkThis command creates and runs a test program that performs a few basic input and output tests. The program will ask for an administrator username and password. Default Firebird installations usually call the database superuser "sysdba" so this user is always a good start. Be sure to provide the name of a database which does not already exist (avoid 'test' which is used on many systems). To keep file permission problems out of this test (more on this below), you may prefer to keep the hostname empty and to specify a directory with write access.If for some reason you need to re-create the autoconf/automake-related files, try running ./autogen.sh.Driver optionsYour application has to initialize libdbi drivers by setting some driver options with the dbi_conn_set_option() and the dbi_conn_set_option_numeric() library functions. The firebird driver supports the following general options:hostThe hostname or IP address of the Firebird database server. Use "localhost" or the real hostname of your local computer to connect to a Firebird server running on the local machine through the network (this is the only way to connect to a local super-server). Do not set the host option if you want to work with a local database, without going through a server.usernameThe name of the user accessing the database.passwordThe password of the user accessing the database.dbnameThe name of the database used for the initial connection. If your program must be able to connect to a fresh Firebird installation, use the test database libdbitest created by make check.encodingThe IANA name of a character encoding which is to be used as the connection encoding. Input and output data will be silently converted from and to this character encoding, respectively. If you set this option to "auto", the connection encoding will be the same as the default encoding of the database.In addition, the following firebird-specific options are supported:firebird_dbdirThis is the directory that holds the Firebird database files. Depending on the settings of the host option, this may refer to a directory on a local or on a remote machine. The ownership and the permissions must match the mode of access. If you create or access a file locally (i.e. with host not set), the account you're logged in needs write and execute permissions. If you set the host, the account your server runs in must have write and execute permissions. This is true even if you connect to your own machine via localhost. Default server installations use the "firebird" account. The database directory should then be owned by firebird:firebird with write and execute permissions for both the user and the group. It should then be sufficient to add yourself to the firebird group to gain access to the database directory.If this option is not specified, a compile-time default directory will be used. Needless to say, this is going to work only if you work on localhost. By default, this directory (usually /usr/local/var/lib/libdbi/firebird) has read and write permissions for everyone with the sticky bit set. If this is not suitable for your application, use a custom directory with your preferred permissions instead.Peculiarities you should know aboutThis chapter lists known peculiarities of the firebird driver. This includes Firebird features that differ from what you know from the other database servers supported by libdbi, and it includes features and misfeatures introduced by the firebird driver. It is the intention of the libdbi developers to reduce the number of misfeatures in future releases if possible.Firebird (mis)featuresTo determine the number of matches, all results have to be retrieved first. This is very inefficient and may provide a bottleneck for large applications.DATETIME and TIME do not appear to support timezoneschar, unsigned char, long long, and unsigned long long types are not supported.GNU Free Documentation LicenseVersion 1.1, March 2000Copyright (C) 2000 Free Software Foundation, Inc. >59 Temple Place, Suite 330, Boston, MA 02111-1307 USA >Everyone is permitted to copy and distribute verbatim copies >of this license document, but changing it is not allowed.0. PREAMBLEThe purpose of this License is to make a manual, textbook, > or other written document "free" in the sense of freedom: to > assure everyone the effective freedom to copy and redistribute it, > with or without modifying it, either commercially or > noncommercially. Secondarily, this License preserves for the > author and publisher a way to get credit for their work, while not > being considered responsible for modifications made by > others.This License is a kind of "copyleft", which means that > derivative works of the document must themselves be free in the > same sense. It complements the GNU General Public License, which > is a copyleft license designed for free software.We have designed this License in order to use it for manuals > for free software, because free software needs free documentation: > a free program should come with manuals providing the same > freedoms that the software does. But this License is not limited > to software manuals; it can be used for any textual work, > regardless of subject matter or whether it is published as a > printed book. We recommend this License principally for works > whose purpose is instruction or reference.1. APPLICABILITY AND DEFINITIONSThis License applies to any manual or other work that > contains a notice placed by the copyright holder saying it can be > distributed under the terms of this License. The "Document", > below, refers to any such manual or work. Any member of the > public is a licensee, and is addressed as "you".A "Modified Version" of the Document means any work > containing the Document or a portion of it, either copied > verbatim, or with modifications and/or translated into another > language.A "Secondary Section" is a named appendix or a front-matter > section of the Document that deals exclusively with the > relationship of the publishers or authors of the Document to the > Document's overall subject (or to related matters) and contains > nothing that could fall directly within that overall subject. > (For example, if the Document is in part a textbook of > mathematics, a Secondary Section may not explain any mathematics.) > The relationship could be a matter of historical connection with > the subject or with related matters, or of legal, commercial, > philosophical, ethical or political position regarding > them.The "Invariant Sections" are certain Secondary Sections > whose titles are designated, as being those of Invariant Sections, > in the notice that says that the Document is released under this > License.The "Cover Texts" are certain short passages of text that > are listed, as Front-Cover Texts or Back-Cover Texts, in the > notice that says that the Document is released under this > License.A "Transparent" copy of the Document means a > machine-readable copy, represented in a format whose specification > is available to the general public, whose contents can be viewed > and edited directly and straightforwardly with generic text > editors or (for images composed of pixels) generic paint programs > or (for drawings) some widely available drawing editor, and that > is suitable for input to text formatters or for automatic > translation to a variety of formats suitable for input to text > formatters. A copy made in an otherwise Transparent file format > whose markup has been designed to thwart or discourage subsequent > modification by readers is not Transparent. A copy that is not > "Transparent" is called "Opaque".Examples of suitable formats for Transparent copies include > plain ASCII without markup, Texinfo input format, LaTeX input > format, SGML or XML using a publicly available DTD, and > standard-conforming simple HTML designed for human modification. > Opaque formats include PostScript, PDF, proprietary formats that > can be read and edited only by proprietary word processors, SGML > or XML for which the DTD and/or processing tools are not generally > available, and the machine-generated HTML produced by some word > processors for output purposes only.The "Title Page" means, for a printed book, the title page > itself, plus such following pages as are needed to hold, legibly, > the material this License requires to appear in the title page. > For works in formats which do not have any title page as such, > "Title Page" means the text near the most prominent appearance of > the work's title, preceding the beginning of the body of the > text.2. VERBATIM COPYINGYou may copy and distribute the Document in any medium, > either commercially or noncommercially, provided that this > License, the copyright notices, and the license notice saying this > License applies to the Document are reproduced in all copies, and > that you add no other conditions whatsoever to those of this > License. You may not use technical measures to obstruct or > control the reading or further copying of the copies you make or > distribute. However, you may accept compensation in exchange for > copies. If you distribute a large enough number of copies you > must also follow the conditions in section 3.You may also lend copies, under the same conditions stated > above, and you may publicly display copies.3. COPYING IN QUANTITYIf you publish printed copies of the Document numbering more > than 100, and the Document's license notice requires Cover Texts, > you must enclose the copies in covers that carry, clearly and > legibly, all these Cover Texts: Front-Cover Texts on the front > cover, and Back-Cover Texts on the back cover. Both covers must > also clearly and legibly identify you as the publisher of these > copies. The front cover must present the full title with all > words of the title equally prominent and visible. You may add > other material on the covers in addition. Copying with changes > limited to the covers, as long as they preserve the title of the > Document and satisfy these conditions, can be treated as verbatim > copying in other respects.If the required texts for either cover are too voluminous to > fit legibly, you should put the first ones listed (as many as fit > reasonably) on the actual cover, and continue the rest onto > adjacent pages.If you publish or distribute Opaque copies of the Document > numbering more than 100, you must either include a > machine-readable Transparent copy along with each Opaque copy, or > state in or with each Opaque copy a publicly-accessible > computer-network location containing a complete Transparent copy > of the Document, free of added material, which the general > network-using public has access to download anonymously at no > charge using public-standard network protocols. If you use the > latter option, you must take reasonably prudent steps, when you > begin distribution of Opaque copies in quantity, to ensure that > this Transparent copy will remain thus accessible at the stated > location until at least one year after the last time you > distribute an Opaque copy (directly or through your agents or > retailers) of that edition to the public.It is requested, but not required, that you contact the > authors of the Document well before redistributing any large > number of copies, to give them a chance to provide you with an > updated version of the Document.4. MODIFICATIONSYou may copy and distribute a Modified Version of the > Document under the conditions of sections 2 and 3 above, provided > that you release the Modified Version under precisely this > License, with the Modified Version filling the role of the > Document, thus licensing distribution and modification of the > Modified Version to whoever possesses a copy of it. In addition, > you must do these things in the Modified Version:Use in the Title Page > (and on the covers, if any) a title distinct from that of the > Document, and from those of previous versions (which should, if > there were any, be listed in the History section of the > Document). You may use the same title as a previous version if > the original publisher of that version gives permission.List on the Title Page, > as authors, one or more persons or entities responsible for > authorship of the modifications in the Modified Version, > together with at least five of the principal authors of the > Document (all of its principal authors, if it has less than > five).State on the Title page > the name of the publisher of the Modified Version, as the > publisher.Preserve all the > copyright notices of the Document.Add an appropriate > copyright notice for your modifications adjacent to the other > copyright notices.Include, immediately > after the copyright notices, a license notice giving the public > permission to use the Modified Version under the terms of this > License, in the form shown in the Addendum below.Preserve in that license > notice the full lists of Invariant Sections and required Cover > Texts given in the Document's license notice.Include an unaltered > copy of this License.Preserve the section > entitled "History", and its title, and add to it an item stating > at least the title, year, new authors, and publisher of the > Modified Version as given on the Title Page. If there is no > section entitled "History" in the Document, create one stating > the title, year, authors, and publisher of the Document as given > on its Title Page, then add an item describing the Modified > Version as stated in the previous sentence.Preserve the network > location, if any, given in the Document for public access to a > Transparent copy of the Document, and likewise the network > locations given in the Document for previous versions it was > based on. These may be placed in the "History" section. You > may omit a network location for a work that was published at > least four years before the Document itself, or if the original > publisher of the version it refers to gives permission.In any section entitled > "Acknowledgements" or "Dedications", preserve the section's > title, and preserve in the section all the substance and tone of > each of the contributor acknowledgements and/or dedications > given therein.Preserve all the > Invariant Sections of the Document, unaltered in their text and > in their titles. Section numbers or the equivalent are not > considered part of the section titles.Delete any section > entitled "Endorsements". Such a section may not be included in > the Modified Version.Do not retitle any > existing section as "Endorsements" or to conflict in title with > any Invariant Section.If the Modified Version includes new front-matter sections > or appendices that qualify as Secondary Sections and contain no > material copied from the Document, you may at your option > designate some or all of these sections as invariant. To do this, > add their titles to the list of Invariant Sections in the Modified > Version's license notice. These titles must be distinct from any > other section titles.You may add a section entitled "Endorsements", provided it > contains nothing but endorsements of your Modified Version by > various parties--for example, statements of peer review or that > the text has been approved by an organization as the authoritative > definition of a standard.You may add a passage of up to five words as a Front-Cover > Text, and a passage of up to 25 words as a Back-Cover Text, to the > end of the list of Cover Texts in the Modified Version. Only one > passage of Front-Cover Text and one of Back-Cover Text may be > added by (or through arrangements made by) any one entity. If the > Document already includes a cover text for the same cover, > previously added by you or by arrangement made by the same entity > you are acting on behalf of, you may not add another; but you may > replace the old one, on explicit permission from the previous > publisher that added the old one.The author(s) and publisher(s) of the Document do not by > this License give permission to use their names for publicity for > or to assert or imply endorsement of any Modified Version.5. COMBINING DOCUMENTSYou may combine the Document with other documents released > under this License, under the terms defined in section 4 above for > modified versions, provided that you include in the combination > all of the Invariant Sections of all of the original documents, > unmodified, and list them all as Invariant Sections of your > combined work in its license notice.The combined work need only contain one copy of this > License, and multiple identical Invariant Sections may be replaced > with a single copy. If there are multiple Invariant Sections with > the same name but different contents, make the title of each such > section unique by adding at the end of it, in parentheses, the > name of the original author or publisher of that section if known, > or else a unique number. Make the same adjustment to the section > titles in the list of Invariant Sections in the license notice of > the combined work.In the combination, you must combine any sections entitled > "History" in the various original documents, forming one section > entitled "History"; likewise combine any sections entitled > "Acknowledgements", and any sections entitled "Dedications". You > must delete all sections entitled "Endorsements."6. COLLECTIONS OF DOCUMENTSYou may make a collection consisting of the Document and > other documents released under this License, and replace the > individual copies of this License in the various documents with a > single copy that is included in the collection, provided that you > follow the rules of this License for verbatim copying of each of > the documents in all other respects.You may extract a single document from such a collection, > and distribute it individually under this License, provided you > insert a copy of this License into the extracted document, and > follow this License in all other respects regarding verbatim > copying of that document.7. AGGREGATION WITH INDEPENDENT WORKSA compilation of the Document or its derivatives with other > separate and independent documents or works, in or on a volume of > a storage or distribution medium, does not as a whole count as a > Modified Version of the Document, provided no compilation > copyright is claimed for the compilation. Such a compilation is > called an "aggregate", and this License does not apply to the > other self-contained works thus compiled with the Document, on > account of their being thus compiled, if they are not themselves > derivative works of the Document.If the Cover Text requirement of section 3 is applicable to > these copies of the Document, then if the Document is less than > one quarter of the entire aggregate, the Document's Cover Texts > may be placed on covers that surround only the Document within the > aggregate. Otherwise they must appear on covers around the whole > aggregate.8. TRANSLATIONTranslation is considered a kind of modification, so you may > distribute translations of the Document under the terms of section > 4. Replacing Invariant Sections with translations requires > special permission from their copyright holders, but you may > include translations of some or all Invariant Sections in addition > to the original versions of these Invariant Sections. You may > include a translation of this License provided that you also > include the original English version of this License. In case of > a disagreement between the translation and the original English > version of this License, the original English version will > prevail.9. TERMINATIONYou may not copy, modify, sublicense, or distribute the > Document except as expressly provided for under this License. Any > other attempt to copy, modify, sublicense or distribute the > Document is void, and will automatically terminate your rights > under this License. However, parties who have received copies, or > rights, from you under this License will not have their licenses > terminated so long as such parties remain in full > compliance.10. FUTURE REVISIONS OF THIS LICENSEThe Free Software Foundation may publish new, revised > versions of the GNU Free Documentation License from time to time. > Such new versions will be similar in spirit to the present > version, but may differ in detail to address new problems or > concerns. See http://www.gnu.org/copyleft/.Each version of the License is given a distinguishing > version number. If the Document specifies that a particular > numbered version of this License "or any later version" applies to > it, you have the option of following the terms and conditions > either of that specified version or of any later version that has > been published (not as a draft) by the Free Software Foundation. > If the Document does not specify a version number of this License, > you may choose any version ever published (not as a draft) by the > Free Software Foundation.How to use this License for your documentsTo use this License in a document you have written, include > a copy of the License in the document and put the following > copyright and license notices just after the title page: Copyright (c) YEAR YOUR NAME. > Permission is granted to copy, distribute and/or modify this document > under the terms of the GNU Free Documentation License, Version 1.1 > or any later version published by the Free Software Foundation; > with the Invariant Sections being LIST THEIR TITLES, with the > Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. > A copy of the license is included in the section entitled "GNU > Free Documentation License".If you have no Invariant Sections, write "with no Invariant > Sections" instead of saying which ones are invariant. If you have > no Front-Cover Texts, write "no Front-Cover Texts" instead of > "Front-Cover Texts being LIST"; likewise for Back-Cover > Texts.If your document contains nontrivial examples of program > code, we recommend releasing these examples in parallel under your > choice of free software license, such as the GNU General Public > License, to permit their use in free software.make[3]: Entering directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >/bin/sh /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/install-sh -d /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/firebird > /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd' > /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0' >Converting dbd_firebird.sgml to HTML... >mkdir -p dbd_firebird && cd dbd_firebird && openjade -t sgml -d ../../../doc/include/doc-html.dsl ../dbd_firebird.sgml > /bin/sh ../../libtool --mode=install /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c libdbdfirebird.la '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd' > /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 dbd_firebird.pdf '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0' >chmod 1777 /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/var/lib/lib/libdbi/firebird >libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libdbdfirebird.so /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd/libdbdfirebird.so >libtool: install: /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c .libs/libdbdfirebird.lai /var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/lib64/dbd/libdbdfirebird.la >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:11:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:13:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:14:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:18:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:19:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:22:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:23:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:29:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:34:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:39:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:44:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:46:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:52:2:E: unknown declaration type "element" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:53:2:E: unknown declaration type "attlist" >openjade:/usr/share/sgml/openjade-1.3.2/dsssl/style-sheet.dtd:76:2:E: entity end not allowed in processing instruction >openjade:../../../doc/include/doc-html.dsl:3:0:E: DTD did not contain element declaration for document type name >openjade:../../../doc/include/doc-html.dsl:2:0:E: notation "dsssl" for entity "docbook.dsl" undefined >openjade:../../../doc/include/doc-html.dsl:5:12:E: element "style-sheet" undefined >openjade:../../../doc/include/doc-html.dsl:6:25:E: there is no attribute "use" >openjade:../../../doc/include/doc-html.dsl:6:34:E: element "style-specification" undefined >openjade:../../../doc/include/doc-html.dsl:7:25:E: element "style-specification-body" undefined >openjade:../../../doc/include/doc-html.dsl:220:27:E: there is no attribute "id" >openjade:../../../doc/include/doc-html.dsl:220:46:E: there is no attribute "document" >openjade:../../../doc/include/doc-html.dsl:220:59:E: element "external-specification" undefined >openjade:../../../doc/include/doc-html.dsl:222:13:E: end tag for "external-specification" omitted, but OMITTAG NO was specified >openjade:../../../doc/include/doc-html.dsl:220:0: start tag was here >openjade:E: specification document does not have the DSSSL architecture as a base architecture >firebird driver manualA libdbi driver providing connectivity to Firebird and Interbase databases.ChristianStamgrenchristian@stamgren.comMarkusHoenickamhoenicka@users.sourceforge.net Permission is granted to copy, distribute and/or modify this > document under the terms of the GNU Free Documentation License, > Version 1.1 or any later version published by the Free Software > Foundation; with no Invariant Sections, with no Front-Cover Texts, > and with no Back-Cover Texts. A copy of the license is included in > . > 0.12008-01-02Prefacelibdbi is a database abstraction layer written in C. It implements a framework that can utilize separate driver libraries for specific database servers. The libdbi-drivers project provides the drivers necessary to talk to the supported database servers.This manual provides information about the Firebird/Interbase driver. The manual is intended for programmers who write applications linked against libdbi and who want their applications to work with Firebird or Interbase database engines.Questions and comments about the Firebird/Interbase driver should be sent to the libdbi-drivers-devel mailing list. Visit the libdbi-drivers-devel list page to subscribe and for further information. Questions and comments about the libdbi library should be sent to the appropriate libdbi mailing list.The Firebird/Interbase driver was developed by Christian Stamgren.IntroductionFirebird is the free cousin of the InterBase SQL database engine, which has a long and winding history related to the repeated reinventions of the Borland, then Inprise, then Borland/Inprise, then again Borland company. Although the internal name of the driver is "firebird", it is supposed to work with the InterBase products as well.InstallationThis chapter describes the prerequisites and the procedures to build and install the firebird driver from the sources.PrerequisitesThe following packages have to be installed on your system:libdbiThis library provides the framework of the database abstraction layer which can utilize the firebird driver to perform database operations. The download page as well as the mailing lists with bug reports and patches are accessible at sourceforge.net/projects/libdbi. The current version of the firebird driver requires libdbi version 0.8.x.libfbembedThis library implements the client API for Firebird/InterBase databases which provides access both locally and through the network. Find the most recent release at www.firebirdsql.org. The current version of the firebird driver was tested with Firebird versions 1.5.3 and 2.0.3 and should work with all recent releases.Build and install the firebird driverFirst you have to unpack the libdbi-drivers archive in a suitable directory. Unpacking will create a new subdirectory libdbi-drivers-X.Y where "X.Y" denotes the version:$ tar -xzf libdbi-drivers-X.Y.tar.gzThe libdbi-drivers project consists of several drivers that use a common build system. Therefore you must tell configure explicitly that you want to build the firebird driver (you can list as many drivers as you want to build):$ cd libdbi-drivers$ ./configure --with-firebirdRun ./configure --help to find out about additional options.Then build the driver with the command:$ makeIf the command results in error messages about the Makefile syntax, you may have to explicitly invoke gmake, the GNU version of make, on your system.Then install the driver with the command (you'll need root permissions to do this):$ make installTo test the operation of the newly installed driver, use the command:$ make checkThis command creates and runs a test program that performs a few basic input and output tests. The program will ask for an administrator username and password. Default Firebird installations usually call the database superuser "sysdba" so this user is always a good start. Be sure to provide the name of a database which does not already exist (avoid 'test' which is used on many systems). To keep file permission problems out of this test (more on this below), you may prefer to keep the hostname empty and to specify a directory with write access.If for some reason you need to re-create the autoconf/automake-related files, try running ./autogen.sh.Driver optionsYour application has to initialize libdbi drivers by setting some driver options with the dbi_conn_set_option() and the dbi_conn_set_option_numeric() library functions. The firebird driver supports the following general options:hostThe hostname or IP address of the Firebird database server. Use "localhost" or the real hostname of your local computer to connect to a Firebird server running on the local machine through the network (this is the only way to connect to a local super-server). Do not set the host option if you want to work with a local database, without going through a server.usernameThe name of the user accessing the database.passwordThe password of the user accessing the database.dbnameThe name of the database used for the initial connection. If your program must be able to connect to a fresh Firebird installation, use the test database libdbitest created by make check.encodingThe IANA name of a character encoding which is to be used as the connection encoding. Input and output data will be silently converted from and to this character encoding, respectively. If you set this option to "auto", the connection encoding will be the same as the default encoding of the database.In addition, the following firebird-specific options are supported:firebird_dbdirThis is the directory that holds the Firebird database files. Depending on the settings of the host option, this may refer to a directory on a local or on a remote machine. The ownership and the permissions must match the mode of access. If you create or access a file locally (i.e. with host not set), the account you're logged in needs write and execute permissions. If you set the host, the account your server runs in must have write and execute permissions. This is true even if you connect to your own machine via localhost. Default server installations use the "firebird" account. The database directory should then be owned by firebird:firebird with write and execute permissions for both the user and the group. It should then be sufficient to add yourself to the firebird group to gain access to the database directory.If this option is not specified, a compile-time default directory will be used. Needless to say, this is going to work only if you work on localhost. By default, this directory (usually /usr/local/var/lib/libdbi/firebird) has read and write permissions for everyone with the sticky bit set. If this is not suitable for your application, use a custom directory with your preferred permissions instead.Peculiarities you should know aboutThis chapter lists known peculiarities of the firebird driver. This includes Firebird features that differ from what you know from the other database servers supported by libdbi, and it includes features and misfeatures introduced by the firebird driver. It is the intention of the libdbi developers to reduce the number of misfeatures in future releases if possible.Firebird (mis)featuresTo determine the number of matches, all results have to be retrieved first. This is very inefficient and may provide a bottleneck for large applications.DATETIME and TIME do not appear to support timezoneschar, unsigned char, long long, and unsigned long long types are not supported.GNU Free Documentation LicenseVersion 1.1, March 2000Copyright (C) 2000 Free Software Foundation, Inc. >59 Temple Place, Suite 330, Boston, MA 02111-1307 USA >Everyone is permitted to copy and distribute verbatim copies >of this license document, but changing it is not allowed.0. PREAMBLEThe purpose of this License is to make a manual, textbook, > or other written document "free" in the sense of freedom: to > assure everyone the effective freedom to copy and redistribute it, > with or without modifying it, either commercially or > noncommercially. Secondarily, this License preserves for the > author and publisher a way to get credit for their work, while not > being considered responsible for modifications made by > others.This License is a kind of "copyleft", which means that > derivative works of the document must themselves be free in the > same sense. It complements the GNU General Public License, which > is a copyleft license designed for free software.We have designed this License in order to use it for manuals > for free software, because free software needs free documentation: > a free program should come with manuals providing the same > freedoms that the software does. But this License is not limited > to software manuals; it can be used for any textual work, > regardless of subject matter or whether it is published as a > printed book. We recommend this License principally for works > whose purpose is instruction or reference.1. APPLICABILITY AND DEFINITIONSThis License applies to any manual or other work that > contains a notice placed by the copyright holder saying it can be > distributed under the terms of this License. The "Document", > below, refers to any such manual or work. Any member of the > public is a licensee, and is addressed as "you".A "Modified Version" of the Document means any work > containing the Document or a portion of it, either copied > verbatim, or with modifications and/or translated into another > language.A "Secondary Section" is a named appendix or a front-matter > section of the Document that deals exclusively with the > relationship of the publishers or authors of the Document to the > Document's overall subject (or to related matters) and contains > nothing that could fall directly within that overall subject. > (For example, if the Document is in part a textbook of > mathematics, a Secondary Section may not explain any mathematics.) > The relationship could be a matter of historical connection with > the subject or with related matters, or of legal, commercial, > philosophical, ethical or political position regarding > them.The "Invariant Sections" are certain Secondary Sections > whose titles are designated, as being those of Invariant Sections, > in the notice that says that the Document is released under this > License.The "Cover Texts" are certain short passages of text that > are listed, as Front-Cover Texts or Back-Cover Texts, in the > notice that says that the Document is released under this > License.A "Transparent" copy of the Document means a > machine-readable copy, represented in a format whose specification > is available to the general public, whose contents can be viewed > and edited directly and straightforwardly with generic text > editors or (for images composed of pixels) generic paint programs > or (for drawings) some widely available drawing editor, and that > is suitable for input to text formatters or for automatic > translation to a variety of formats suitable for input to text > formatters. A copy made in an otherwise Transparent file format > whose markup has been designed to thwart or discourage subsequent > modification by readers is not Transparent. A copy that is not > "Transparent" is called "Opaque".Examples of suitable formats for Transparent copies include > plain ASCII without markup, Texinfo input format, LaTeX input > format, SGML or XML using a publicly available DTD, and > standard-conforming simple HTML designed for human modification. > Opaque formats include PostScript, PDF, proprietary formats that > can be read and edited only by proprietary word processors, SGML > or XML for which the DTD and/or processing tools are not generally > available, and the machine-generated HTML produced by some word > processors for output purposes only.The "Title Page" means, for a printed book, the title page > itself, plus such following pages as are needed to hold, legibly, > the material this License requires to appear in the title page. > For works in formats which do not have any title page as such, > "Title Page" means the text near the most prominent appearance of > the work's title, preceding the beginning of the body of the > text.2. VERBATIM COPYINGYou may copy and distribute the Document in any medium, > either commercially or noncommercially, provided that this > License, the copyright notices, and the license notice saying this > License applies to the Document are reproduced in all copies, and > that you add no other conditions whatsoever to those of this > License. You may not use technical measures to obstruct or > control the reading or further copying of the copies you make or > distribute. However, you may accept compensation in exchange for > copies. If you distribute a large enough number of copies you > must also follow the conditions in section 3.You may also lend copies, under the same conditions stated > above, and you may publicly display copies.3. COPYING IN QUANTITYIf you publish printed copies of the Document numbering more > than 100, and the Document's license notice requires Cover Texts, > you must enclose the copies in covers that carry, clearly and > legibly, all these Cover Texts: Front-Cover Texts on the front > cover, and Back-Cover Texts on the back cover. Both covers must > also clearly and legibly identify you as the publisher of these > copies. The front cover must present the full title with all > words of the title equally prominent and visible. You may add > other material on the covers in addition. Copying with changes > limited to the covers, as long as they preserve the title of the > Document and satisfy these conditions, can be treated as verbatim > copying in other respects.If the required texts for either cover are too voluminous to > fit legibly, you should put the first ones listed (as many as fit > reasonably) on the actual cover, and continue the rest onto > adjacent pages.If you publish or distribute Opaque copies of the Document > numbering more than 100, you must either include a > machine-readable Transparent copy along with each Opaque copy, or > state in or with each Opaque copy a publicly-accessible > computer-network location containing a complete Transparent copy > of the Document, free of added material, which the general > network-using public has access to download anonymously at no > charge using public-standard network protocols. If you use the > latter option, you must take reasonably prudent steps, when you > begin distribution of Opaque copies in quantity, to ensure that > this Transparent copy will remain thus accessible at the stated > location until at least one year after the last time you > distribute an Opaque copy (directly or through your agents or > retailers) of that edition to the public.It is requested, but not required, that you contact the > authors of the Document well before redistributing any large > number of copies, to give them a chance to provide you with an > updated version of the Document.4. MODIFICATIONSYou may copy and distribute a Modified Version of the > Document under the conditions of sections 2 and 3 above, provided > that you release the Modified Version under precisely this > License, with the Modified Version filling the role of the > Document, thus licensing distribution and modification of the > Modified Version to whoever possesses a copy of it. In addition, > you must do these things in the Modified Version:Use in the Title Page > (and on the covers, if any) a title distinct from that of the > Document, and from those of previous versions (which should, if > there were any, be listed in the History section of the > Document). You may use the same title as a previous version if > the original publisher of that version gives permission.List on the Title Page, > as authors, one or more persons or entities responsible for > authorship of the modifications in the Modified Version, > together with at least five of the principal authors of the > Document (all of its principal authors, if it has less than > five).State on the Title page > the name of the publisher of the Modified Version, as the > publisher.Preserve all the > copyright notices of the Document.Add an appropriate > copyright notice for your modifications adjacent to the other > copyright notices.Include, immediately > after the copyright notices, a license notice giving the public > permission to use the Modified Version under the terms of this > License, in the form shown in the Addendum below.Preserve in that license > notice the full lists of Invariant Sections and required Cover > Texts given in the Document's license notice.Include an unaltered > copy of this License.Preserve the section > entitled "History", and its title, and add to it an item stating > at least the title, year, new authors, and publisher of the > Modified Version as given on the Title Page. If there is no > section entitled "History" in the Document, create one stating > the title, year, authors, and publisher of the Document as given > on its Title Page, then add an item describing the Modified > Version as stated in the previous sentence.Preserve the network > location, if any, given in the Document for public access to a > Transparent copy of the Document, and likewise the network > locations given in the Document for previous versions it was > based on. These may be placed in the "History" section. You > may omit a network location for a work that was published at > least four years before the Document itself, or if the original > publisher of the version it refers to gives permission.In any section entitled > "Acknowledgements" or "Dedications", preserve the section's > title, and preserve in the section all the substance and tone of > each of the contributor acknowledgements and/or dedications > given therein.Preserve all the > Invariant Sections of the Document, unaltered in their text and > in their titles. Section numbers or the equivalent are not > considered part of the section titles.Delete any section > entitled "Endorsements". Such a section may not be included in > the Modified Version.Do not retitle any > existing section as "Endorsements" or to conflict in title with > any Invariant Section.If the Modified Version includes new front-matter sections > or appendices that qualify as Secondary Sections and contain no > material copied from the Document, you may at your option > designate some or all of these sections as invariant. To do this, > add their titles to the list of Invariant Sections in the Modified > Version's license notice. These titles must be distinct from any > other section titles.You may add a section entitled "Endorsements", provided it > contains nothing but endorsements of your Modified Version by > various parties--for example, statements of peer review or that > the text has been approved by an organization as the authoritative > definition of a standard.You may add a passage of up to five words as a Front-Cover > Text, and a passage of up to 25 words as a Back-Cover Text, to the > end of the list of Cover Texts in the Modified Version. Only one > passage of Front-Cover Text and one of Back-Cover Text may be > added by (or through arrangements made by) any one entity. If the > Document already includes a cover text for the same cover, > previously added by you or by arrangement made by the same entity > you are acting on behalf of, you may not add another; but you may > replace the old one, on explicit permission from the previous > publisher that added the old one.The author(s) and publisher(s) of the Document do not by > this License give permission to use their names for publicity for > or to assert or imply endorsement of any Modified Version.5. COMBINING DOCUMENTSYou may combine the Document with other documents released > under this License, under the terms defined in section 4 above for > modified versions, provided that you include in the combination > all of the Invariant Sections of all of the original documents, > unmodified, and list them all as Invariant Sections of your > combined work in its license notice.The combined work need only contain one copy of this > License, and multiple identical Invariant Sections may be replaced > with a single copy. If there are multiple Invariant Sections with > the same name but different contents, make the title of each such > section unique by adding at the end of it, in parentheses, the > name of the original author or publisher of that section if known, > or else a unique number. Make the same adjustment to the section > titles in the list of Invariant Sections in the license notice of > the combined work.In the combination, you must combine any sections entitled > "History" in the various original documents, forming one section > entitled "History"; likewise combine any sections entitled > "Acknowledgements", and any sections entitled "Dedications". You > must delete all sections entitled "Endorsements."6. COLLECTIONS OF DOCUMENTSYou may make a collection consisting of the Document and > other documents released under this License, and replace the > individual copies of this License in the various documents with a > single copy that is included in the collection, provided that you > follow the rules of this License for verbatim copying of each of > the documents in all other respects.You may extract a single document from such a collection, > and distribute it individually under this License, provided you > insert a copy of this License into the extracted document, and > follow this License in all other respects regarding verbatim > copying of that document.7. AGGREGATION WITH INDEPENDENT WORKSA compilation of the Document or its derivatives with other > separate and independent documents or works, in or on a volume of > a storage or distribution medium, does not as a whole count as a > Modified Version of the Document, provided no compilation > copyright is claimed for the compilation. Such a compilation is > called an "aggregate", and this License does not apply to the > other self-contained works thus compiled with the Document, on > account of their being thus compiled, if they are not themselves > derivative works of the Document.If the Cover Text requirement of section 3 is applicable to > these copies of the Document, then if the Document is less than > one quarter of the entire aggregate, the Document's Cover Texts > may be placed on covers that surround only the Document within the > aggregate. Otherwise they must appear on covers around the whole > aggregate.8. TRANSLATIONTranslation is considered a kind of modification, so you may > distribute translations of the Document under the terms of section > 4. Replacing Invariant Sections with translations requires > special permission from their copyright holders, but you may > include translations of some or all Invariant Sections in addition > to the original versions of these Invariant Sections. You may > include a translation of this License provided that you also > include the original English version of this License. In case of > a disagreement between the translation and the original English > version of this License, the original English version will > prevail.9. TERMINATIONYou may not copy, modify, sublicense, or distribute the > Document except as expressly provided for under this License. Any > other attempt to copy, modify, sublicense or distribute the > Document is void, and will automatically terminate your rights > under this License. However, parties who have received copies, or > rights, from you under this License will not have their licenses > terminated so long as such parties remain in full > compliance.10. FUTURE REVISIONS OF THIS LICENSEThe Free Software Foundation may publish new, revised > versions of the GNU Free Documentation License from time to time. > Such new versions will be similar in spirit to the present > version, but may differ in detail to address new problems or > concerns. See http://www.gnu.org/copyleft/.Each version of the License is given a distinguishing > version number. If the Document specifies that a particular > numbered version of this License "or any later version" applies to > it, you have the option of following the terms and conditions > either of that specified version or of any later version that has > been published (not as a draft) by the Free Software Foundation. > If the Document does not specify a version number of this License, > you may choose any version ever published (not as a draft) by the > Free Software Foundation.How to use this License for your documentsTo use this License in a document you have written, include > a copy of the License in the document and put the following > copyright and license notices just after the title page: Copyright (c) YEAR YOUR NAME. > Permission is granted to copy, distribute and/or modify this document > under the terms of the GNU Free Documentation License, Version 1.1 > or any later version published by the Free Software Foundation; > with the Invariant Sections being LIST THEIR TITLES, with the > Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. > A copy of the license is included in the section entitled "GNU > Free Documentation License".If you have no Invariant Sections, write "with no Invariant > Sections" instead of saying which ones are invariant. If you have > no Front-Cover Texts, write "no Front-Cover Texts" instead of > "Front-Cover Texts being LIST"; likewise for Back-Cover > Texts.If your document contains nontrivial examples of program > code, we recommend releasing these examples in parallel under your > choice of free software license, such as the GNU General Public > License, to permit their use in free software. /usr/bin/mkdir -p '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0/dbd_firebird' > /usr/lib/portage/python3.11/ebuild-helpers/xattr/install -c -m 644 ./dbd_firebird/* '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/image/usr/share/doc/libdbi-drivers-0.9.0/dbd_firebird' >libtool: warning: remember to run 'libtool --finish /usr/lib64/dbd' >install: cannot stat './dbd_firebird/*': No such file or directory >make[3]: *** [Makefile:549: install-htdocDATA] Error 1 >make[3]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >make[2]: *** [Makefile:666: install-am] Error 2 >make[2]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers/firebird' >make[1]: *** [Makefile:406: install-recursive] Error 1 >make[1]: Leaving directory '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0/drivers' >make: *** [Makefile:458: install-recursive] Error 1 > * ERROR: dev-db/libdbi-drivers-0.9.0-r1::gentoo failed (install phase): > * emake failed > * > * If you need support, post the output of `emerge --info '=dev-db/libdbi-drivers-0.9.0-r1::gentoo'`, > * the complete build log and the output of `emerge -pqv '=dev-db/libdbi-drivers-0.9.0-r1::gentoo'`. > * The complete build log is located at '/var/log/portage/dev-db:libdbi-drivers-0.9.0-r1:20230917-022040.log'. > * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/temp/environment'. > * Working directory: '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' > * S: '/var/tmp/portage/dev-db/libdbi-drivers-0.9.0-r1/work/libdbi-drivers-0.9.0' >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 914346
:
870781
| 870782 |
870783
|
870784
|
870785
|
870786
|
870787
|
870788