1 |
> -----Original Message----- |
2 |
> From: Mike Frysinger [mailto:vapier@g.o] |
3 |
> Sent: Saturday, January 26, 2008 5:17 AM |
4 |
> |
5 |
> > > |
6 |
> > > ok ... but does that solve your problem ? |
7 |
> > |
8 |
> > Yes, this does solve gdbm's problem. I tried the newly emerged gdbm |
9 |
and |
10 |
> > was able to create large data bases beyond the ~2GB file size limit. |
11 |
I |
12 |
> > generated 3.1GB databases and twice as large. |
13 |
> > |
14 |
> > Will the ebuild change be a part of future ebuild versions? |
15 |
|
16 |
Will I have to modify the gdbm ebuild in the future as I update my |
17 |
gentoo systems? Or will the ebuild be modified in future versions? |
18 |
|
19 |
Thanks, |
20 |
|
21 |
-- |
22 |
Valmor |
23 |
|
24 |
> > |
25 |
> > I have exchanged e-mails with the gdbm maintainer and he said |
26 |
databases |
27 |
> > written with 32bit off_t will not be read/modified by gdbm when |
28 |
compiled |
29 |
> > with 64bit off_t. |
30 |
> |
31 |
> that's because you're only changing how gdbm interfaces with the C |
32 |
> library. |
33 |
> you arent changing the gdbm API/ABI. |
34 |
> -mike |
35 |
-- |
36 |
gentoo-devhelp@l.g.o mailing list |