Open FireBoyAJ24 opened 1 month ago
Hey. Thanks for letting me know.
I think the best thing to do would be to have a minimal c/c++ code example to be able to reproduce this outside of the OMPL build context. So I can try to write a test case for it and debug it.
I do not have an ARM machine right now (might buy a ARM Mac next year though). I need to check if I can set ARM CI on Github, I think they announced ARM machines lately.
The bug might also be in CastXML. Another solution would be to provide the xml files that have been generated, because I think I can also explore their content and see what is going on.
Description
When building the OMPL
make update_bindings
on ARM, we get an error:pygccxml.declarations.runtime_errors.multiple_declarations_found_t: Multiple declarations have been found. Matcher: [(decl type==namespace_t) and (name==std)]
. Context of this issue comes from https://github.com/ompl/ompl/issues/1116.Is it possible that the standard C++ library headers are treated differently (unexpectedly) in ARM compared to X86_64 in PygccXML?
I placed this issue in pygccxml as the error comes from this package compared to py++ and OMPL.
Expected Behavior
In X86_64, we are able to make the Python bindings with no errors. However, in ARM, we get the error stated in the description.
Example Code to Test the Error
Example util.h file:
Error:
Tried Potential Solutions
FILE_BY_FILE
) instead ofALL_AT_ONCE
and was able to build the util module but got the same multiple declaration error in other packages (base, geometric, etc).Resources