I guess we need to define FB_USE_SIZE_T macros while configure. But I'm not sure I understand a comment of Nikolay. How changing one place can fix different places when 8 bytes are assigned to 4. Or in such places we need to use 4 bytes size_t which FB_SIZE_T does? If so the fix is simple and local: change the crash like like
bufAligned = (char*) FB_ALIGN((U_IPTR) bufAligned, (size_t)SYS_PAGE_SIZE); In this case FB can be built but I'm not sure about correctness of this and cannot imagine other places when the problems can happen. 2014-07-19 16:22 GMT+04:00 Dmitry Yemanov <firebi...@yandex.ru>: > 19.07.2014 14:14, Roman Simakov wrote: > >> IMO FB must use system size_t. > > We were using system size_t until Nickolay had committed FB_SIZE_T a few > days ago in attempt to avoid warnings. The bad thing is that it wasnt't > discussed. > > > Dmitry > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel -- Roman Simakov ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
