On Sun, 06 Jul 2008 19:03:36 +0200 (CEST) Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> Here is a sample of cpp input which is based on >> my previous post. I tested on: >> >> * Mac OS X 10.4 on G3 PowerPC (default is LP32) >> * HP-UX 11 on IA64 & HP C compiler (default is LP32. +DD64 makes LP64). >> * AIX 5.2 on ppc64 & Hitachi C compiler (default is LP32. -64 makes LP64). >> * GNU/Linux (glibc-2.7) on amd64 & gcc-3.3 (default is LP64, -m32 makes >> LP32). >> * GNU/Linux (glibc-2.7) on i386 & Tiny C compiler (default is LP32). >> * FreeBSD 4.11 on i386 & gcc-2.95.4 (LP32 but inttypes.h has uint64_t). >> * FreeBSD 6.2 on amd64 & gcc-3.4.6 (default is LP64, -m32 makes LP64). > >Thanks a lot for your great analysis and code! Please install >whatever you think is appropriate. Thank you for positive comment. As a quick fix for this issue, I will commit this, after small cleanup. I guess the requirement of single config.h supporting multiple arch/data-model/ABIs might be popular, so I posted to autoconf list for further discussion toward to generic solution. >> Also the requirement of support for 16bit-integer platform >> should be discussed. Yet I don't have any good system to >> run configure - anybody has access to legacy Minix for 8086? > >Hmm. What about running, say, the emx compiler in an MSDOS shell >within a BOCHS (or DOSEMU) session? A longer time ago I did this to >check whether 16bit support still works. It might be a good exercise >to test this again. Reason: 16bit compilers might detect problems not >visible to 32bit compilers. Also thank you for the information, I was not aware of emx compiler, I will try. At present, the most easiest 16bit environment in Debian GNU/Linux might be Bruce's C compiler and ELKS, but it's oriented to GNU/Linux, I want to test on more older 16bit systems. Regards, mpsuzuki _______________________________________________ Freetype-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype-devel
