Gentoo Archives: gentoo-devhelp

From: Mike Frysinger <vapier@g.o>
To: gentoo-devhelp@l.g.o
Cc: "de Almeida, Valmor F." <dealmeidav@××××.gov>
Subject: Re: [gentoo-devhelp] gdbm ebuild with 64bit off_t
Date: Sat, 26 Jan 2008 10:17:18
Message-Id: 200801260517.14278.vapier@gentoo.org
In Reply to: RE: [gentoo-devhelp] gdbm ebuild with 64bit off_t by "de Almeida
On Friday 25 January 2008, de Almeida, Valmor F. wrote:
> > -----Original Message----- > > From: Mike Frysinger [mailto:vapier@g.o] > > Sent: Wednesday, January 23, 2008 5:33 PM > > > > > Never dealt with ebuild files before; did some reading and then > > > > > > cd /usr/portage/sys-libs/gdbm/ > > > ebuild gdbm-1.8.3-r3.ebuild digest > > > emerge gdbm > > > > > > Noticed that gcc now uses > > > > > > -D_FILE_OFFSET_BITS=64 > > > > ok ... but does that solve your problem ? > > Yes, this does solve gdbm's problem. I tried the newly emerged gdbm and > was able to create large data bases beyond the ~2GB file size limit. I > generated 3.1GB databases and twice as large. > > Will the ebuild change be a part of future ebuild versions? > > I have exchanged e-mails with the gdbm maintainer and he said databases > written with 32bit off_t will not be read/modified by gdbm when compiled > with 64bit off_t.
that's because you're only changing how gdbm interfaces with the C library. you arent changing the gdbm API/ABI. -mike

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies