summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-08-10 15:54:54 +0000
committerUlrich Drepper <drepper@redhat.com>1998-08-10 15:54:54 +0000
commita5f4e34a264b7cd296f8ca890ca4eaa1d0f99317 (patch)
treeba02529e747024948875e5f6eb93c1676a9d2144 /FAQ.in
parent0e94359046d83b56f1b15ff00c4b2f75499bf8c3 (diff)
Update.
1998-08-10 15:49 Ulrich Drepper <drepper@cygnus.com> * include/dirent.h: Protect from double inclusion. 1998-08-09 Mark Kettenis <kettenis@phys.uva.nl> * posix/glob.h: Add LFS support for glob and globfree. * posix/Versions [GLIBC_2.1]: Add glob64 and globfree64. * posix/Makefile (routines): Add glob64. * sysdeps/generic/glob64.c: New file. * sysdeps/unix/sysv/linux/glob64.c: New file. * sysdeps/unix/sysv/linux/alpha/glob64.c: New file. * sysdeps/unix/sysv/linux/sparc/sparc64/glob64.c: New file. * sysdeps/generic/glob.c [_LIBC && glob] (__glob_pattern_p): Elide function. * sysdeps/unix/sysv/linux/alpha/glob.c: Add glob64 as a weak alias for __new_glob. Likewise for globfree64. * sysdeps/unix/sysv/linux/sparc/sparc64/glob.c: New file. 1998-08-09 Andreas Schwab <schwab@issan.informatik.uni-dortmund.de> * sysdeps/unix/Makefile ($(common-objpfx)s-proto.d): Remove -include flag from command.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in15
1 files changed, 15 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index 4f65022b0c..c4bafc0c55 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -997,6 +997,21 @@ e.g. __ivaliduser). If a program uses these interfaces, it's broken. These
internal interfaces might change between glibc releases or dropped
completely.
+?? When using the db-2 library which comes with glibc is used in
+ the Perl db modules the testsuite is not passed. This did not
+ happen with db-1, gdbm, or ndbm.
+
+{UD} You are using an outdated copy of the DB_File Perl module. In fact db-2
+finally removed the handling of zero-sized keys which was one of the features
+tested by the old Perl testsuite and therefore you see an error. But this
+never was documented and guaranteed, only broken programs used this feature.
+
+Consequently db-2 does not need to support this feature and instead signals
+an error which leads to easier debugging. The DB_File module maintainer
+Paul Marquess <pmarquess@bfsec.bt.co.uk> acknowledged this change and fixed
+the testsuite so that if you use DB_File v1.60 or later you should not have
+any more problems with db-2.
+
? Miscellaneous