On Wed, 2009-12-16 at 09:56 -0500, Jeffrey Stedfast wrote:
> This just means the proper LARGEFILE flags are not being used at
> compile time. Either EDS's configure isn't doing proper checks or else
> Evolution itself isn't doing proper checks and there is some sort of clash.
> An easy way to fix this is to do what I did with GMime, which is to
> simply make all public stream APIs that use off_t use goffset instead
> (I'm sure Matthew will want to do this anyway). Then the problem is
> much simpler to solve - just make sure that Camel uses the proper CFLAGS
> for LARGEFILE support (which you can steal from GMime's configure
> scripts).

IIRC, the issue is LARGEFILE support is still disabled by default, and
there was concern that simply turning it on would somehow break existing
installs.  I'm fuzzy on the details, but vaguely recall it being about a
field size in some binary file being dependent on sizeof(off_t), which
would change with LARGEFILE support enabled and thus break the binary

Unfortunately I don't remember which file that was an issue in.  It may
have already been addressed by the move to a summary database, or I may
just be propagating false rumors.

I'm mightily tempted to just enable it by default and see what breaks.
Can't be much worse than the issues we're already haunted by.

Matthew Barnes

Evolution-hackers mailing list

Reply via email to