[shmem] compile time error with mingw (uint64_t)
Hi, Thats my second posting for this error, but in the first one I've done a error in reasoning. I get this error when I try to compile my application with mingw in Windows. ./boost/shmem/sync/xtime.hpp: In function `int boost::shmem::xtime_get(boost::shmem::xtime*, int)': ./boost/shmem/sync/xtime.hpp:91: error: integer constant is too large for "long" type The line which produce this error message is the following. static const boost::uint64_t timespec_to_filetime_offset = (boost::uint64_t)(116444736000000000); Firstly I thought that I've a configuration problem and uint64_t is defined with "long" or "unsigned long" and cannot hold this 64 bit constant, but it was wrong. uint64_t has just like the constant 64 bit - sizeof(boost::uint64_t) returns 8. If I replace boost::uint64_t with "unsigned long long" the same error occures. But unsigned has no sign bit and should hold exactly 64 bit values. I've absolutely no idea. What's wrong??? Thank you in advance for every reply, Sascha
Hello, The newest version of shmem has a fix in, the constant needs an L after it to tell the compiler its a long value. Thanks
Jan Have a look at the earlier post by Sascha too. This is my original post on this matter so take a look at that too: http://article.gmane.org/gmane.comp.lib.boost.user/19353/match=mingw+shmem Thanks
Thank you all for help. Sorry that I'am not up-to-date with reading the list. Sascha Jan Stetka schrieb:
Jan
Have a look at the earlier post by Sascha too. This is my original post on this matter so take a look at that too: http://article.gmane.org/gmane.comp.lib.boost.user/19353/match=mingw+shmem
Thanks
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Hi, Sorry for not replying your previous mail. The sandbox-cvs code should work for MinGW and contains some bug-fixes. I wanted to release a new (0.94) Shmem package but I'm currently quite busy with Interprocess documentation and testing. But I should definitely release a new official version as soon as I can. Jan previously reported this error and suggested a fix, so if you downloaded the latest code, should work fine on MinGW. Regards, Ion
participants (3)
-
Ion Gaztañaga
-
Jan Stetka
-
Sascha Lumma