|Re: [AD] Fwd: Re: Allegro 188.8.131.52 + latest MinGW = off_t undefined|
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
Meant to send this to the mailing list. Sorry bout that.
-------- Forwarded Message --------
Subject: Re: [AD] Allegro 184.108.40.206 + latest MinGW = off_t undefined Date: Mon, 17 Oct 2016 17:32:25 -0500 From: Edgar Reynaldo <EdgarReynaldo@xxxxxxxxxx. allegro.cc> To: Elias Pschernig <elias@xxxxxxxxxxxx>
On 10/9/2016 10:01 AM, Elias Pschernig wrote:
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 <siegelordex@xxxxxxxxxx> wrote:
Sounds like the proper solution is to define _POSIX_C_SOURCE then, perhaps guarded by a check for ALLEGRO_GCC.
All of these errors have been fixed by patches issued by Keith Marshall of MinGW, as detailed here :
So as far as I can see, Allegro 5 programs now properly compile with the C++11 standard in use.
Do we really need to replace off_t with int64_t though? I mean better safe than sorry, but are we really ever going to deal with file system entries larger than 4GB? Where does the issue with using off_t on 64 bit systems come in? If we needed file system offsets I would agree that int64_t would be better, but I don't see any of that in use at the moment.
Allegro-developers mailing list
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|