Skip to content

pyxis: fix include path so <slurm/spank.h> resolves with a custom slurm_install_prefix - #1388

Open
100milliongold wants to merge 1 commit into
NVIDIA:masterfrom
xiilab:fix/pyxis-include-path
Open

pyxis: fix include path so <slurm/spank.h> resolves with a custom slurm_install_prefix#1388
100milliongold wants to merge 1 commit into
NVIDIA:masterfrom
xiilab:fix/pyxis-include-path

Conversation

@100milliongold

Copy link
Copy Markdown

Problem

roles/pyxis/tasks/pyxis.yml passes -I {{ slurm_install_prefix }}/include/slurm to the pyxis build, but pyxis sources #include <slurm/spank.h>, so the compiler looks for .../include/slurm/slurm/spank.h. With the default prefix (/usr/local) this is masked because /usr/local/include is already on the compiler's default search path. With any other prefix the build fails:

pyxis_dispatch.c:5:10: fatal error: slurm/spank.h: No such file or directory

Reproduced on DGX OS 7.5.0 with slurm_install_prefix: /raid/slurm/usr/local (DeepOps master, Slurm 26.05.3, pyxis 0.11.1).

Fix

Pass -I {{ slurm_install_prefix }}/include instead. One-line change; behaviour with the default prefix is unchanged.

Verification

After the change, make -j in /usr/local/src/pyxis completes and the slurm-cluster playbook proceeds past the pyxis role on the system above.

…rm_install_prefix

The build task passed -I {{ slurm_install_prefix }}/include/slurm, but
pyxis sources include <slurm/spank.h>, so the compiler looked for
.../include/slurm/slurm/spank.h. With the default prefix (/usr/local)
this went unnoticed because /usr/local/include is on the compiler's
default search path. With any other prefix the build fails:

  pyxis_dispatch.c:5:10: fatal error: slurm/spank.h: No such file or directory

Pass -I {{ slurm_install_prefix }}/include instead.

Observed on DGX OS 7.5.0 with slurm_install_prefix=/raid/slurm/usr/local
(DeepOps master, Slurm 26.05.3, pyxis 0.11.1). After the change the
pyxis build completes.

Signed-off-by: Jea-Eok-Kim <je.kim@xiilab.com>
@100milliongold
100milliongold marked this pull request as ready for review September 3, 2026 13:40
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.

2 participants