Skip to content
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

use <boost/bind/bind.hpp> + using namespace boost::placeholders #43

Closed
robtaylor opened this issue Sep 21, 2023 · 2 comments · Fixed by #44
Closed

use <boost/bind/bind.hpp> + using namespace boost::placeholders #43

robtaylor opened this issue Sep 21, 2023 · 2 comments · Fixed by #44

Comments

@robtaylor
Copy link
Collaborator

/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
[530/1084] Compiling C++ object hurric...c/viewer/libviewer.a.p/CellImage.cpp.o
In file included from /usr/include/boost/bind.hpp:30,
                 from ../hurricane/src/viewer/CellImage.cpp:21:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
@jpc-lip6
Copy link
Collaborator

I did make the fix, it worked on my AlmaLinux 9, but failed on the github workflow that uses Ubuntu...

@robtaylor
Copy link
Collaborator Author

robtaylor commented Sep 22, 2023 via email

@jpc-lip6 jpc-lip6 linked a pull request Sep 22, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants