| 1 |
> -----Original Message----- |
| 2 |
> From: Mike Frysinger [mailto:vapier@g.o] |
| 3 |
> Sent: Tuesday, January 22, 2008 11:15 PM |
| 4 |
> |
| 5 |
> > The reason is that as it stands now, gdbm-1.8.3-r3 on 32bit machines |
| 6 |
can |
| 7 |
> > only work with data base files of about 2 GB since off_t is 4 bytes. |
| 8 |
If |
| 9 |
> > gdbm is built with off_t size equal to 8 bytes, it will handle much |
| 10 |
> > larger database files. |
| 11 |
> |
| 12 |
> can you describe the issue you're looking a bit more ? |
| 13 |
|
| 14 |
When emerging gdbm-1.8.3-r3 on my system, off_t is 4 bytes. Therefore |
| 15 |
the gdbm files are of about 2 GB maximum size. Trying to create |
| 16 |
databases with greater sizes results in |
| 17 |
|
| 18 |
gdbm fatal: write error |
| 19 |
|
| 20 |
If gdbm is built with off_t defined as 8 bytes, much larger gdbm files |
| 21 |
can be created. However previous database files created with off_t of 4 |
| 22 |
bytes cannot be modified or read. |
| 23 |
|
| 24 |
I am wondering whether gdbm could be built with this flexibility. |
| 25 |
|
| 26 |
|
| 27 |
Thanks, |
| 28 |
|
| 29 |
-- |
| 30 |
Valmor |
| 31 |
|
| 32 |
|
| 33 |
->emerge --info |
| 34 |
Portage 2.1.3.19 (default-linux/x86/2007.0, gcc-4.1.2, glibc-2.6.1-r0, |
| 35 |
2.6.22.9 i686) |
| 36 |
================================================================= |
| 37 |
System uname: 2.6.22.9 i686 Intel(R) Xeon(TM) CPU 2.60GHz |
| 38 |
Timestamp of tree: Sat, 17 Nov 2007 04:30:01 +0000 |
| 39 |
app-shells/bash: 3.2_p17 |
| 40 |
dev-java/java-config: 1.3.7, 2.0.33-r1 |
| 41 |
dev-lang/python: 2.4.4-r6 |
| 42 |
dev-python/pycrypto: 2.0.1-r6 |
| 43 |
sys-apps/baselayout: 1.12.9-r2 |
| 44 |
sys-apps/sandbox: 1.2.18.1-r2 |
| 45 |
sys-devel/autoconf: 2.13, 2.61-r1 |
| 46 |
sys-devel/automake: 1.6.3, 1.7.9-r1, 1.9.6-r2, 1.10 |
| 47 |
sys-devel/binutils: 2.18-r1 |
| 48 |
sys-devel/gcc-config: 1.3.16 |
| 49 |
sys-devel/libtool: 1.5.24 |
| 50 |
virtual/os-headers: 2.6.22-r2 |
| 51 |
ACCEPT_KEYWORDS="x86" |
| 52 |
CBUILD="i686-pc-linux-gnu" |
| 53 |
CFLAGS="-O3 -march=pentium4 -pipe" |
| 54 |
CHOST="i686-pc-linux-gnu" |
| 55 |
|
| 56 |
> |
| 57 |
> > It would be helpful if there were a USE 64bit option for emerging |
| 58 |
gdbm. |
| 59 |
> |
| 60 |
> mmm, that's not the way to approach this issue |
| 61 |
> -mike |
| 62 |
-- |
| 63 |
gentoo-devhelp@l.g.o mailing list |
Archives