Skip to content
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

[TRIVIAL] Workarounds for gcc-13 compatibility #4817

Merged
merged 2 commits into from
Dec 1, 2023

Conversation

Bronek
Copy link
Collaborator

@Bronek Bronek commented Nov 16, 2023

High Level Overview of Change

Workaround for compilation errors with gcc-13 and other compilers relying on libstdc++ version 13

This is temporary until actual fix boostorg/beast#2682 is available for us to use.

Context of Change

Some boost.beast files (which we do use) rely on an old gcc-12 behaviour where #include <cstdint> was not needed even though types from this header were used. This was broken by change in libstdc++ version 13 https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes . The necessary fix was implemented in boost.beast in boostorg/beast#2682 however it is not yet available. Until it is available we can use this workaround to enable compilation of rippled with gcc-13, clang-16 etc.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (you added tests for code that already exists, or your new feature included in this PR)
  • Documentation update
  • Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
  • Release

@Bronek Bronek marked this pull request as ready for review November 29, 2023 16:02
@Bronek Bronek changed the title Workarounds for gcc-13 compatibility [TRIVIAL] Workarounds for gcc-13 compatibility Nov 30, 2023
@intelliot intelliot merged commit 06251aa into XRPLF:develop Dec 1, 2023
8 checks passed
@intelliot
Copy link
Collaborator

Merged due to request from Bronek and because the change is trivial.

sophiax851 pushed a commit to sophiax851/rippled that referenced this pull request Jun 12, 2024
Workaround for compilation errors with gcc-13 and other compilers
relying on `libstdc++` version 13. This is temporary until actual fix is
available for us to use: boostorg/beast#2682

Some boost.beast files (which we do use) rely on an old gcc-12 behaviour
where `#include <cstdint>` was not needed even though types from this
header were used. This was broken by a change in libstdc++ version 13:
https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes

The necessary fix was implemented in boost.beast, however it is not yet
available. Until it is available, we can use this workaround to enable
compilation of `rippled` with gcc-13, clang-16, etc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants