Web lists-archives.com

Re: [Mingw-users] errno_t and strerror_s


Thank you for looking into this. The whole problem arises because cmake incorrectly detects strerror_s in MinGW gcc 5.3.0. Allegro uses strerror_r and strerror_s when they are available and so latest Allegro from GIT fails to build because they are not actually present. The call to cmake's check_function_exists(strerror_s) incorrectly reports it's presence. This is with latest cmake installed. I plan to report it to cmake soon. If MinGW provided a strerror_r function it would solve this problem nicely. But like you said, it needs to be thread safe. That's why allegro is using them. In other cases it simply reports an empty string.

Thanks for your efforts,

Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
MinGW-users mailing list

This list observes the Etiquette found at 
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at:
Also: mailto:mingw-users-request@xxxxxxxxxxxxxxxxxxxxx?subject=unsubscribe