On 05-Sep-14 00:01, Kurt Roeckx wrote: > On Tue, Sep 13, 2005 at 08:46:24PM +0200, Andreas Jochens wrote: > > Using 'intptr_t' will lead to problems because older C environments do > > not know about it and sometimes 'configure' scripts do ugly things with > > 'intptr_t'. As an example, 'e2fsprogs' broke with gcc-4.0 because it > > used 'intptr_t'. > > intptr_t exists for about 10 years now, in either inttypes.h > or stdint.h. And if something breaks you should fix it. It's > not that hard to make proper configure checks.
I had to fix about 50 packages which failed with gcc-4.0 because of ugly configure checks for intptr_t and other type definitions. So it seems to be hard to write portable configure checks. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
