-
Notifications
You must be signed in to change notification settings - Fork 44
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
Build error on Rolling #65
Comments
Hello, @ralph-lange @JanStaschulat @norro could you please check that? I guess that there are changes in RCL lifecycle and incompatibility with RCLC Rolling. Thanks a lot! |
Yep, also fails on the build farm since yesterday: https://build.ros2.org/job/Rbin_uF64__rclc_lifecycle__ubuntu_focal_amd64__binary/37/ to https://build.ros2.org/job/Rbin_uF64__rclc_lifecycle__ubuntu_focal_amd64__binary/40/ |
All micro-ROS CI are failing in Rolling. Does your team have some time to fix this @ralph-lange? Or maybe I should find a temporal solution like disabling this package for micro-ROS? Sorry for the inconvenience. |
@pablogs9 I probably can find some time today or tomorrow to fix rclc_lifecycle. /cc @ralph-lange |
Thank you for taking care of this, @norro. The relevant change to rcl_lifecycle can be found at ros2/rcl#882. |
Thanks a lot @norro @ralph-lange !! |
documentation: |
@anaelle-sw The changes have been merged to the master branch (i.e. for Rolling release). Does this fix your problems? |
Yes, I can build micro-ROS! Thanks a lot! |
* fixed corrupted CHANGELOG.rst Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com> * updated changelog Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com> * 0.1.7 Co-authored-by: Ralph Lange <ralph-lange@users.noreply.github.com>
Steps to reproduce the issue
Hello,
I tried to build the latest version from micro-ROS Arduino, but a build error occurred:
This last command failed:
Additional information
@pablogs9 gave me the following information:
this is an RCLC problem because they have not updated their RCL API usage in Rolling. These are the changes: ros2/rcl@e9b588d
The text was updated successfully, but these errors were encountered: