[18431] Fix missing includes

[JLBuenoLopez]

Description

@Mergifyio backport 2.9.x 2.6.x 2.1.x

Fixes #3494

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• [N/A] Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• [N/A] Any new/modified methods have been properly documented using Doxygen.
• Changes are ABI compatible.
• Changes are API compatible.
• [N/A] New feature has been added to the versions.md file (if applicable).
• [N/A] New feature has been documented/Current behavior is correctly described in the documentation.
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[MiguelCompany]

LGTM with green build

[JLBuenoLopez]

@richiprosima please test this

[skrede]

Could this change be made to 2.10.x as well? In its current state, this prevents ROS2 from building on systems with GCC 13.1, as ROS2 specifically targets the 2.10.x branch.

https://github.com/ros2/ros2/blob/rolling/ros2.repos

[MiguelCompany]

@skrede It is already in 2.10.x: commit add29f4

[JLBuenoLopez]

@Mergifyio backport 2.9.x 2.6.x

[mergify]

backport 2.9.x 2.6.x

✅ Backports have been created

• #3517 [18431] Fix missing includes (backport #3508) has been created for branch 2.9.x
• #3518 [18431] Fix missing includes (backport #3508) has been created for branch 2.6.x

[indeedhat]

Could this get back ported to 2.6.4 as required by ros2 humble-release please

[JLBuenoLopez]

@indeedhat, these changes have already been backported into 2.6.x in #3518. These changes will be included in the next patch release: 2.6.5. Until that moment, just build using 2.6.x branch or the commit that introduces the changes 02539b9. Fast DDS policy is not to change published releases.

[indeedhat]

that makes sense, thanks

[kistlin]

I think the same happens in the latest release v2.11.0, when building the statistics backend.

To fix it, the following change was necessary.

diff --git a/include/fastdds/dds/core/status/StatusMask.hpp b/include/fastdds/dds/core/status/StatusMask.hpp
index c838ff369..2718869d7 100644
--- a/include/fastdds/dds/core/status/StatusMask.hpp
+++ b/include/fastdds/dds/core/status/StatusMask.hpp
@@ -24,6 +24,7 @@
 #include <fastrtps/fastrtps_dll.h>

 #include <bitset>
+#include <cstdint>
 #include <sstream>

 //!Alias of size_t(16)