> My question is: where should I look and/or what should I change, to > make them act the same?
The FT_INT64 stuff is only used in a single file, `src/base/ftcalc.c'. However, AFAIK, the GNU C compiler always defines a 64bit data type (`long long int'), so I'm really surprised that you experience this problem. Perhaps this is different for GNU C on ARM? Can you try make devel make (from a fresh tarball) for compiling FreeType so that you bypass the `configure' script? Do you then get correct results for your demo application? Can you please also post the file `builds/unix/config.log' (compressed)? > In particular, it appears to me that the ARM system is doing some > incorrect math from the metrics width value of 0x2C0 to get 0x800, > but I'm having trouble identifying why this might be. Finally, can you decorate the various functions of ftcalc.c with some printf calls to find out where the difference comes from? Up to now, we've never received a similar problem report. Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel