Skip to content

new(mysql.com/v5_7): MySQL 5.7 legacy (Top 300 #735)#13062

Open
tannevaled wants to merge 4 commits into
pkgxdev:mainfrom
tannevaled:new/mysql-v5-7
Open

new(mysql.com/v5_7): MySQL 5.7 legacy (Top 300 #735)#13062
tannevaled wants to merge 4 commits into
pkgxdev:mainfrom
tannevaled:new/mysql-v5-7

Conversation

@tannevaled
Copy link
Copy Markdown
Contributor

EOL line still pinned by some legacy apps. Build expected to need CI iteration.

🤖 Generated with Claude Code

5.7 reached EOL 2023-10. Some legacy apps (Rails 5.x, legacy
WordPress, custom replication setups) still pin to it. CMake
policy version override applied for the vendored boost.

Closes part of pkgxdev#99 (holdout pkgxdev#735). Build expected
to need iteration — 5.7 + modern toolchain is rough.
@tannevaled tannevaled marked this pull request as draft May 29, 2026 13:41
@tannevaled
Copy link
Copy Markdown
Contributor Author

Draft — MySQL 5.7's vendored InnoDB has non-standard C++ idioms (unnamed scoped enums in univ.i:418) that gcc 12+ rejects:

storage/innobase/include/univ.i:418:33:
  error: unnamed scoped enum is not allowed

Same family of problems as cubefs/RocksDB (#13050): the C++ standard has tightened and old MySQL 5.7 needs either gcc 8 (not in pantry) or source patches across many files.

MySQL 5.7 has been EOL since Oct 2023; homebrew dropped its formula in 2024. The right call may be to mark this as 'not viable from-source' rather than spend more cycles patching.

@tannevaled tannevaled marked this pull request as ready for review May 29, 2026 13:56
@tannevaled
Copy link
Copy Markdown
Contributor Author

Reopened — using new gnu.org/gcc/v8 recipe (#13070) for the legacy InnoDB compile. Same approach as cubefs (#13050). Builds once #13070 lands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant