Or maybe replace off_t with int64_t - the uses I can see seem very suspicious, and most likely currently Allegro 5 will break if it is ever compiled on a system where off_t is only 32 bit.
On Sat, Oct 8, 2016 at 9:59 PM, SiegeLord <[email protected]> wrote: > Sounds like the proper solution is to define _POSIX_C_SOURCE then, perhaps > guarded by a check for ALLEGRO_GCC. > > -SL > > On 10/08/2016 06:31 PM, Edgar Reynaldo wrote: > >> Hello, >> >> I started a thread about this on a.cc : >> >> https://www.allegro.cc/forums/thread/616526 >> >> Basically, when you compile an allegro program with the latest MinGW >> runtime >> (3.21.1 or 3.22.2) and use -std=c++11, you get errors saying off_t is >> undefined. >> >> mingw/include/sys/types.h defines off_t, but only in certain cases, >> such as when _POSIX_C_SOURCE is defined before including it >> (in mingwrt 3.22.2) or when _NO_OLDNAMES is undefined (in mingwrt 3.21.1). >> >> So allegro programs compiled with -std=c++11 fail to compile. >> >> What should we do? >> >> Edgar >> >> >> _______________________________________________ >> Allegro-developers mailing list >> [email protected] >> https://mail.gna.org/listinfo/allegro-developers >> > > _______________________________________________ > Allegro-developers mailing list > [email protected] > https://mail.gna.org/listinfo/allegro-developers >
_______________________________________________ Allegro-developers mailing list [email protected] https://mail.gna.org/listinfo/allegro-developers
