>From a related thread: "One of these days we need to fix all this ... basically migrate to purely 64-bit file offset platforms. It should "just work" without any changes needed at that point, if they do it right (which is not a given). If old programs compiled on legacy 32-bit file offset platforms break, so be it. "
Dont'cha just love it -- the "fix" is just to say "screw it" to anybody who's not running 64-bit. Hasn't been fixed in years, although it's been known about for years. Robert, if your fix is that simple, then why the FSCK haven't the good folks at Evolution, Gnome, or Ubuntu done it? Just tell everyone to throw away every computer that isn't 64-bit. Why do they even bother to produce a 32-bit version, then? (can you tell I'm exhausted and irritated? Been up most of the past two nights with a different computer problem for ByteWorks) Theresa On Mon, 2009-11-30 at 08:27 -0500, Robert Citek wrote: > On Mon, Nov 30, 2009 at 12:24 AM, Theresa Kehoe <[email protected]> wrote: > > On Sun, 2009-11-29 at 22:24 -0500, Robert Citek wrote: > >> I searched on launchpad for folder size in evolution, but I don't see it: > >> > >> https://bugs.launchpad.net/evolution/+bugs?field.searchtext=folder+size > >> > >> Do you have a link to the bug report? > > > > https://bugzilla.gnome.org/show_bug.cgi?id=522433 > > Which references this: > > https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/197290 > > Many years ago perl under Red Hat did not come packaged with large > file support. The solution was to rebuild the package with the > parameter enabling large file support. Evolution under Ubuntu may > require a similar solution. > > Rebuilding the package under Red Hat was fairly simple, a one-liner if > I recall correctly. Unfortunately, I don't know how to do the > equivalent under Ubuntu/Debian. > > If we wanted to go down that route, I would start by having a simple > test, ideally a test case that anyone can create and use quickly. In > this case, a simple test would be to somehow create (i.e. a script or > command) a mail folder with a mailfile that is 1.9 GB and another mail > folder with a mailfile that is 2.2 GB. > > Once we have a test, then it's a mater of using Evolution to open one > then the other mailfile, rebuild, and repeat, until Evolution can open > both mailfiles. > > The solution may be as simple as adding the gcc flag > -D_FILE_OFFSET_BITS=64 when compiling Evolution, or it may be as > complicated as adding the gcc flag -D_FILE_OFFSET_BITS=64 to every > single Evolution dependency. > > Regards, > - Robert > -- Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug
