Skip to content

Updates from macOS testing: openblas, openmpi, libiconv#53

Draft
mathomp4 wants to merge 4 commits intoJCSDA:spack-stack-devfrom
GMAO-SI-Team:mathomp4-updates-2026Apr16
Draft

Updates from macOS testing: openblas, openmpi, libiconv#53
mathomp4 wants to merge 4 commits intoJCSDA:spack-stack-devfrom
GMAO-SI-Team:mathomp4-updates-2026Apr16

Conversation

@mathomp4
Copy link
Copy Markdown
Collaborator

In my current testing with spack-stack and macOS, I found I needed to update three packages used in GEOS:

  • libiconv
  • openblas
  • openmpi

In each case, I checked out the mothership spack package:

git fetch official
git checkout official/develop -- \
  repos/spack_repo/builtin/packages/openblas \
  repos/spack_repo/builtin/packages/libiconv \
  repos/spack_repo/builtin/packages/openmpi

This seems to be working in my testing so far, but I'm leaving this draft.

Also, I'd like to make sure @climbfuji can look and see if maybe I shouldn't be pulling from official for these? The openmpi package seems quite different. Though maybe that's just from age?

@mathomp4 mathomp4 self-assigned this Apr 16, 2026
@mathomp4 mathomp4 requested a review from climbfuji April 16, 2026 17:46
Copy link
Copy Markdown
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

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

I don't see any problem with these updates. Let's make sure they work as expected in spack-stack CI. I may also want to test on my WSL2 laptops.

# all versions of icx up to 2025.
# https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/All-versions-of-icx-miscompile-error-0-resulting-in-segfaults/m-p/1744208
if self.spec.satisfies("%oneapi@:2025"):
args.append("gl_cv_func_working_error=yes")
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This is good to have!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Oh. I didn't even notice that! Was that from you? :)

@mathomp4
Copy link
Copy Markdown
Collaborator Author

I don't see any problem with these updates. Let's make sure they work as expected in spack-stack CI. I may also want to test on my WSL2 laptops.

Should I make a PR to spack-stack updating the submodule to see how the CI responds?

@climbfuji
Copy link
Copy Markdown
Collaborator

I don't see any problem with these updates. Let's make sure they work as expected in spack-stack CI. I may also want to test on my WSL2 laptops.

Should I make a PR to spack-stack updating the submodule to see how the CI responds?

Yes please

@mathomp4
Copy link
Copy Markdown
Collaborator Author

I don't see any problem with these updates. Let's make sure they work as expected in spack-stack CI. I may also want to test on my WSL2 laptops.

Should I make a PR to spack-stack updating the submodule to see how the CI responds?

Yes please

@climbfuji I just did JCSDA/spack-stack#1990 but I might have done the git wrong. Weirdly, I see your p4est and py_protobuf changes in that test PR? I mean, my changes are there too but...huh.

@climbfuji
Copy link
Copy Markdown
Collaborator

climbfuji commented Apr 16, 2026

I don't see any problem with these updates. Let's make sure they work as expected in spack-stack CI. I may also want to test on my WSL2 laptops.

Should I make a PR to spack-stack updating the submodule to see how the CI responds?

Yes please

@climbfuji I just did JCSDA/spack-stack#1990 but I might have done the git wrong. Weirdly, I see your p4est and py_protobuf changes in that test PR? I mean, my changes are there too but...huh.

because JCSDA/spack-stack#1988 isn't merged yet

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