Dominique Pelle wrote: > > Then we could not use the autoconf check, it always defines uint32_t. > > > > I'll undefine uint32_t in vim.h, like it's done for netbeans. > > > The same kind of error still happens when compiling if_python.c: > > In file included from /usr/local/include/python2.6/pyport.h:7, > from /usr/local/include/python2.6/Python.h:58, > from if_python.c:49: > /usr/include/stdint.h:52: error: duplicate ‘unsigned’ > /usr/include/stdint.h:52: error: two or more data types in declaration > specifiers > > > Shouldn't we include <stdint.h> (introduced in c99) rather than defining > int32_t when stdint.h is available? With something more or less like... > > #ifdef HAVE_STDINT_H > #include <stdint.h> > #else > /* Define to `unsigned int' or other type that is 32 bit. */ > #define uint32_t unsigned int > #endif
stdint.h is a C99 thing. I would rather avoid using C99 features. Unfortunately, it appears it gets dragged in anyway indirectly. We can't #define uint32_t directly, the sizeof(int) is undefined. Please try the current version, hopefully this works for everyone. -- hundred-and-one symptoms of being an internet addict: 70. ISDN lines are added to your house on a hourly basis /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
