Thanks to visit codestin.com
Credit goes to github.com

Skip to content

dockerfiles: use NINJA_VERSION instead of CMAKE_VERSION for ./install_ninja.sh#5580

Open
scottt wants to merge 1 commit into
ROCm:mainfrom
scottt:dockerfiles-fix-ninja-version-variable-name
Open

dockerfiles: use NINJA_VERSION instead of CMAKE_VERSION for ./install_ninja.sh#5580
scottt wants to merge 1 commit into
ROCm:mainfrom
scottt:dockerfiles-fix-ninja-version-variable-name

Conversation

@scottt
Copy link
Copy Markdown
Contributor

@scottt scottt commented Jun 2, 2026

This trivial patch changes the Ninja version string in build_manylinux_x86_64.Dockerfile from the currently misnamed CMAKE_VERSION to NINJA_VERSION.

@stellaraccident reused CMAKE_VERSION as the name for the variable passed to ./install_ninja.sh in 02db71e for build_manylinux_x86_64.Dockerfile. build_manylinux_rccl_x86_64.Dockerfile then inherited that when it was created in cd0270b

Motivation

I create Dockerfiles for more recent Linux distro releases and build TheRock in them to stay one step ahead of breakage from e.g. newer toolchains. Having the CMAKE_VERSION and NINJA_VERSION be distinctly named makes my scripts to sync up the build dependencies easier.

Submission Checklist

Copy link
Copy Markdown
Contributor

@JeniferC99 JeniferC99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rename is incomplete: the RUN ./install_ninja.sh "${CMAKE_VERSION}" line on the next row still references ${CMAKE_VERSION}, which is still defined ("3.27.9") from the CMake block above.

Comment thread dockerfiles/build_manylinux_x86_64.Dockerfile Outdated
Comment thread dockerfiles/build_manylinux_rccl_x86_64.Dockerfile Outdated
…_ninja.sh

This trivial patch changes the Ninja version string in `build_manylinux_x86_64.Dockerfile` from
the currently misnamed `CMAKE_VERSION` to `NINJA_VERSION`.

Stella used `CMAKE_VERSION` for the version passed to `./install_ninja.sh` in 02db71e for
`build_manylinux_x86_64.Dockerfile`. `build_manylinux_rccl_x86_64.Dockerfile` then inherited
that when it was created in cd0270b

I create Dockerfiles for more recent Linux distro releases and build TheRock in them to
stay one step ahead of breakage from e.g. newer toolchains.
Having the CMAKE_VERSION and NINJA_VERSION be distinctly named makes my scripts to sync up the build dependencies easier.
@scottt scottt force-pushed the dockerfiles-fix-ninja-version-variable-name branch from b2fa0e5 to 778a8f7 Compare June 3, 2026 08:49
@scottt
Copy link
Copy Markdown
Contributor Author

scottt commented Jun 3, 2026

The rename is incomplete: the RUN ./install_ninja.sh "${CMAKE_VERSION}" line on the next row still references ${CMAKE_VERSION}, which is still defined ("3.27.9") from the CMake block above.

@JeniferC99 , thanks for catching this! Resolved in the latest version.

@scottt scottt requested a review from JeniferC99 June 3, 2026 19:37
Copy link
Copy Markdown
Contributor

@JeniferC99 JeniferC99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@JeniferC99 JeniferC99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry actually, please don't fork it, instead branch it from main so the CI can run naturally.

Copy link
Copy Markdown
Contributor

@JeniferC99 JeniferC99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like I can approve the workflow to run manually. back to +1

@scottt
Copy link
Copy Markdown
Contributor Author

scottt commented Jun 4, 2026

@JeniferC99 , since all CI check passed. could you press the Github "merge" button for me as I can't do it myself as an external contributor?

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

Labels

None yet

Projects

Status: TODO

Development

Successfully merging this pull request may close these issues.

2 participants