Dear Sirs, Oh sorry - now I'm absent from my office during 3 days, please let me work in this weekend.
Regards, mpsuzuki Werner LEMBERG wrote: >> I have got to the bottom of the latter issue; I mentioned that I was >> cross-compiling, for apple, right? > > Ah, I've missed that. Toshiya-san, could you have a look, please? > The code in question is yours :-) > >> It really needs the --enable-biarch-config switch: >> >> without --enable-biarch-config: >> >> checking size of long... 8 >> checking whether cpp computation of bit length in ftconfig.in >> works... no >> >> with --enable-biarch-config: >> >> checking size of long... 8 >> checking whether cpp computation of bit length in ftconfig.in >> works... broken but use it >> >> I don't know where it gets the size of long from. The apple >> compiler front end is quite interesting in that it drives the >> individual architectures and put all three (or 4) outputs from >> 32-bit powerpc, 32-bit intel, 64-bit intel into 1 "object" files. >> And the warnings come from the "under the hood" compile of the >> 32-bit outputs. >> >> The 32-bit powerpc and 32-bit intel arch have size of long = 4. If >> I use the individual single architecture front end, then it shows >> "4" and "yes" respectively. >> >> I am wondering whether --enable-biarch-config should be better >> documented, and/or made the default for Mac OS X? (though it >> probably make less sense now since apple has moved to 64-bit intel >> somewhat exclusively lately) >> >> Also, can it not use stdint.h and int64_t directly? "long" is rather >> vague :-). >> >>> /root/rpmbuild/BUILD/freetype-2.5.4/src/base/fttrigon.c:74: >>> warning: right shift count >= width of type _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel