1 |
> -----Original Message----- |
2 |
> From: Mike Frysinger [mailto:vapier@g.o] |
3 |
> Sent: Wednesday, January 23, 2008 5:33 PM |
4 |
> |
5 |
> > Never dealt with ebuild files before; did some reading and then |
6 |
> > |
7 |
> > cd /usr/portage/sys-libs/gdbm/ |
8 |
> > ebuild gdbm-1.8.3-r3.ebuild digest |
9 |
> > emerge gdbm |
10 |
> > |
11 |
> > Noticed that gcc now uses |
12 |
> > |
13 |
> > -D_FILE_OFFSET_BITS=64 |
14 |
> |
15 |
> ok ... but does that solve your problem ? |
16 |
> -mike |
17 |
|
18 |
Yes, this does solve gdbm's problem. I tried the newly emerged gdbm and |
19 |
was able to create large data bases beyond the ~2GB file size limit. I |
20 |
generated 3.1GB databases and twice as large. |
21 |
|
22 |
Will the ebuild change be a part of future ebuild versions? |
23 |
|
24 |
I have exchanged e-mails with the gdbm maintainer and he said databases |
25 |
written with 32bit off_t will not be read/modified by gdbm when compiled |
26 |
with 64bit off_t. |
27 |
|
28 |
Thanks, |
29 |
|
30 |
-- |
31 |
Valmor |
32 |
-- |
33 |
gentoo-devhelp@l.g.o mailing list |