Skip to content

v6.0.x: Use compiler basename in ltmain_flang_darwin patch#13804

Open
billsacks wants to merge 1 commit intoopen-mpi:v6.0.xfrom
billsacks:fix_flang_darwin_patch_v6.0
Open

v6.0.x: Use compiler basename in ltmain_flang_darwin patch#13804
billsacks wants to merge 1 commit intoopen-mpi:v6.0.xfrom
billsacks:fix_flang_darwin_patch_v6.0

Conversation

@billsacks
Copy link
Copy Markdown
Contributor

Checking $CC directly fails if the compiler is given with a full path (e.g., in a Spack-based build). This change fixes the check of the compiler to use the basename, as is done in a few other places.

(cherry picked from commit fc7fa11)

Resolves #13770 for the v6.0.x branch. (See also #13771 for the corresponding PR to main: this is a back-port of that PR.)

I haven't tested this with the v6.0.x branch or with the main branch; I did test the conceptually equivalent changes in the v5.0.x branch (see #13772 ). As I noted in #13771 , I am concerned that the patch here may not apply cleanly to libtool's ltmain.sh, and this may need to be changed to the version on the v5.0.x branch.

Checking $CC directly fails if the compiler is given with a full path
(e.g., in a Spack-based build). This change fixes the check of the
compiler to use the basename, as is done in a few other places.

Signed-off-by: Bill Sacks <sacks@ucar.edu>
(cherry picked from commit fc7fa11)
@github-actions github-actions bot added this to the v6.0.0 milestone Apr 2, 2026
@billsacks
Copy link
Copy Markdown
Contributor Author

As with the versions on v5.0.x and main: Credit goes to @mcmehrtens for pointing out the problem and suggested fix in https://groups.google.com/a/lists.open-mpi.org/g/users/c/4mIxq9op75k

@billsacks
Copy link
Copy Markdown
Contributor Author

@ggouaillardet - since I think you put in place the original fix in #13142 , are you able to comment on why the patch on main (which is the same as the one here, in the v6.0.x branch) differs from the patch on the v5.0.x branch? (i.e., why did your added patch in #13162 differ from your added patch in #13142?) I'm concerned that the patch on main and here seems like it won't apply cleanly to libtool's ltmain.sh. But I could easily be missing something - I have very little knowledge of this area.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant