1.1

> -----Original Message-----
> From: Mike Frysinger [mailto:vapier@g.o]
> Sent: Tuesday, January 22, 2008 11:15 PM
> 
> > The reason is that as it stands now, gdbm-1.8.3-r3 on 32bit machines
can
> > only work with data base files of about 2 GB since off_t is 4 bytes.
If
> > gdbm is built with off_t size equal to 8 bytes, it will handle much
> > larger database files.
> 
> can you describe the issue you're looking a bit more ?

When emerging gdbm-1.8.3-r3 on my system, off_t is 4 bytes. Therefore
the gdbm files are of about 2 GB maximum size. Trying to create
databases with greater sizes results in

gdbm fatal: write error

If gdbm is built with off_t defined as 8 bytes, much larger gdbm files
can be created. However previous database files created with off_t of 4
bytes cannot be modified or read.

I am wondering whether gdbm could be built with this flexibility.


Thanks,

--
Valmor


->emerge --info
Portage 2.1.3.19 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.6.1-r0,
2.6.22.9 i686)
=================================================================
System uname: 2.6.22.9 i686 Intel(R) Xeon(TM) CPU 2.60GHz
Timestamp of tree: Sat, 17 Nov 2007 04:30:01 +0000
app-shells/bash:     3.2_p17
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.6.3, 1.7.9-r1, 1.9.6-r2, 1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.22-r2
ACCEPT_KEYWORDS="x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"

> 
> > It would be helpful if there were a USE 64bit option for emerging
gdbm.
> 
> mmm, that's not the way to approach this issue
> -mike
--
gentoo-devhelp@g.o mailing list