Re: [Mac-on-linux-devel] Bug#435136: [Mac-on-linux-users] Compiling binaries failed

[Joseph J. <jo...@ge...>]

> Whatever is going on there is no way that including stdio.h prior to
> zlib.h should break anything (or be required for that matter).  I've
> just had a brief look and as far as I can tell it works perfectly well
> with either _LARGEFILE64_SOURCE or _FILE_OFFSET_BITS set with both 1.2.3
> and 1.2.3.3 (the latter is what's in Debian unstable but is a
> pre-release so most people are at 1.2.3).  If there *are* problems with
> the zlib headers it would be best to work out what they are and try to
> resolve them prior to the next zlib release.
> 
> The only thing I can think that might break is if blk_dmg.h tries to set
> one or the other of those defines after stdio.h has been included.
> 
> Note that I've no idea what version of Mac on Linux Elimar was
> experiencing trouble with and have been entirely unable to reproduce the
> problem he is reporting.  If someone could provide reproduction
> instructions or (better yet) a cut down test case I could have a look.
> 
> Note also that the gzio API in zlib prior to 1.2.3.mumble prereleases
> doesn't cope with large files at all, though you don't seem to be using
> it so that shouldn't be an issue.
> 

I've also been unable to reproduce it here on Gentoo.  To be honest, 
I don't see how including/not including stdio.h should make a 
difference either way, which is why I just removed it.  Again, if a 
FC7 user would like to test the current SVN for me, I'd appreciate it.

Thanks,
-Joe