fix for endian mismatch issue per boostorg/python PR #218 #292
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jwhendy
changed the title
This was referenced Sep 28, 2019
|
I can confirm that this fixes the message of the RuntimeError: FATAL: module compiled as little endian, but detected different endianness at runtime
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/hgaiser/dev/fizyr/ros/cv_bridge/devel_isolated/cv_bridge/lib/python3.8/site-packages/cv_bridge/__init__.py", line 35, in <module>
exec(__fh.read())
File "<string>", line 6, in <module>
SystemError: initialization of cv_bridge_boost raised unreported exceptionSo now it was actually crashing code. The proposed change fixes this issue for me. |
2maz
added a commit
to rock-simulation/mars
that referenced
this pull request
Apr 30, 2020
RuntimeError: FATAL: module compiled as little endian, but detected different endianness at runtime see also ros-perception/vision_opencv#292 and ros-melodic-arch/ros-melodic-cv-bridge#2
2maz
added a commit
to rock-simulation/mars
that referenced
this pull request
Apr 30, 2020
RuntimeError: FATAL: module compiled as little endian, but detected different endianness at runtime see also ros-perception/vision_opencv#292 and ros-melodic-arch/ros-melodic-cv-bridge#2
jacobperron
reviewed
Jul 9, 2020
| @@ -37,6 +37,7 @@ PyObject* pyopencv_from(const cv::Mat& m); | |||
| static int do_numpy_import( ) | |||
There was a problem hiding this comment.
Should we update the signature to void *? This is what I'm proposing in the equivalent ros2 patch (#346).
|
Closing, as this has been superceded by #323 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Greetings,
I'm on a team maintanining arch linux packages for ROS and someone just ran into this issue. Namely, upon import the user gets:
In googling around, I found this and this which were handled by PRs boostorg/python 218 and python-pni 74. Both were the same, and appear based on this explanation.
I grepped for
import_array, added thereturn NULLstatement, rebuilt, and I no longer get the import error.