From: Neil M. <nm...@zi...> - 2001-11-17 02:15:25
|
On Fri, Nov 16, 2001 at 08:55:47PM +0100, Pavel Cisar wrote: > On 16 Nov 2001, at 7:14, John Bellardo wrote: > > We need to add a flag or something to the build process that defines > > that macro on mixed 32/64 bit platforms (like linux) to make it easy to > > do both builds. The lack of that mechanism is the only reason a 64 bit > > build of RC1 isn't done yet (and maybe time, too). > > I did the 64 bit RC1 Linux version, but I haven't enough time to test > it to the extent that would satisfy me. So we decided to do not > slow down the (eagerly awaited) RC1 release by it. This is the basically the situation with 64bit IO for Solaris as well. I have have working on it during the last couple of weeks and it has ended requiring more changes than expected due to conflicts with ib_stdio. Classic engine is reading/writing big db ok from isql, gstat/gfix ok, gbak can generate a backup file > 2Gb ok but restoring a database fails at the 2Gb point. This is odd because the open/write procedures it uses on the database are the same pio routines used by isql which operate on a >2Gb database with out problem. Trussing gbak shows it using opening/creating the new database with the 64bit version of open, any suggestions very welcome. Super engine seems ok for everything - it uses pread/pwrite which needed changing - but as I don't use super it has had only basic testing. My current plan is to build clean 32bit only versions for the release files and a 64bit super as a snapshot build with the differences as a patch within the cvs. -- Neil McCalden @home nm...@zi... |