-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MinGW32 compilation errors #116
Comments
BTW, there is |
I suspect that nobody is using the plain MinGW (as opposed to mingw-w64) anymore, but I have no way to know for sure. For the time being I've removed (the old) MinGW from my Appveyor. We'll see if anyone (apart from you) notices. |
Yeah, there was an |
using msvc and C++20 the same issues with _snprintf
|
look at there |
@marakew This looks like In any case, this is not the issue that was reported here. |
i think remove "using std::snprintf;" solve this
there non sense use std::snprintf inside boost::system::detail
|
You have |
drop "using std::snprintf" will be better solution
|
This is not a solution at all. Any |
not
and how this was work before commit mention above ?
|
It will be more convenient for me because it will avoid bug reports such as yours, so I may well do that, but it's not a better solution overall, because you'll keep encountering these issues in other libraries until you fix your code to remove the #define. |
As long as you have the Note that |
This compiler is no longer supported by Boost.System. boostorg/system#116
This compiler is no longer supported by Boost.System. boostorg/system#116
This compiler is no longer supported by Boost.System. boostorg/system#116
* Update thread_safety_checking.cpp to use Standard Library types * Remove MinGW runs due to boostorg/system#116 * Delete the shared memory example sources
Looks like 44582f3 and possibly some other recent commits broke MinGW32 builds of Boost.Filesystem:
https://ci.appveyor.com/project/Lastique/filesystem/builds/48983852/job/2cgottx8b8ckwac0?fullLog=true#L376
Is this platform no longer supported?
The text was updated successfully, but these errors were encountered: