[Fontconfig] Porting, binary files, and releases

Patrick Lam plam at MIT.EDU
Thu Feb 9 08:24:11 PST 2006

Matthias Clasen wrote:
> On Thu, 2006-02-09 at 10:53 -0500, Patrick Lam wrote:
>>Doodle wrote:
>>>The code uses fopen() at some places, and uses open() at some other.
>>>Shouldn't this be unified? Anyway, the open flag O_BINARY is missing
>>>from the open() of the cache file handling routines, which caused
>>>problems with the font-cache on OS/2 GCC (where the default is text file).
>>Um, O_BINARY doesn't exist for me under Linux.  I better not commit
>>that.  Someone (not me) is going to have to be a bit more clever than
>>that.  rsync defines its own O_BINARY to 0 if the platform doesn't
>>provide it.  You might want to start with the binary.patch I've attached.
> The GLib mmap wrapper just does 
> #ifndef _O_BINARY
> #define _O_BINARY 0
> #endif

This doesn't quite get us any further ahead; I'd imagine that some
config-fu would be involved in doing the right thing on a variety of


More information about the Fontconfig mailing list