-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Pybind11 no longer compiles with GCC 7.2 and Python 2.7 #1804
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
Comments
Hi Michael, our travis CI suite tests GCC on Linux, with Python 2.7, which at least seems to pass the test suite: https://travis-ci.org/pybind/pybind11/jobs/544890337 Can you clarify on how your setup is different? Best, |
btw, these are actually warnings that get turned into errors due to your addition of a -Werror flag. |
One option might be to simply include that header a few lines before. Does the following patch fix things? diff --git a/include/pybind11/pybind11.h b/include/pybind11/pybind11.h
index f1d91c7..0cc5dd5 100644
--- a/include/pybind11/pybind11.h
+++ b/include/pybind11/pybind11.h
@@ -41,16 +41,15 @@
# endif
#endif
-#if defined(__GNUG__) && !defined(__clang__)
- #include <cxxabi.h>
-#endif
-
-
#include "attr.h"
#include "options.h"
#include "detail/class.h"
#include "detail/init.h"
+#if defined(__GNUG__) && !defined(__clang__)
+# include <cxxabi.h>
+#endif
+
NAMESPACE_BEGIN(PYBIND11_NAMESPACE)
/// Wraps an arbitrary C++ function/method/lambda function/.. into a callable Python object |
We are using GCC version 7.2. Perhaps that is the difference. |
Yes, that patch fixes things. |
Merged, will be part of v2.3.1 |
Updated to 2.3.0 and this killed my tests (with |
Uh oh!
There was an error while loading. Please reload this page.
Pybind11 no longer compiles with GCC and Python 2.7
I get the following errors when compiling with v2.3.0:
I believe this is introduced by commit: 69dc380
The text was updated successfully, but these errors were encountered: