Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building findutils fails on macOS #17

Closed
climbfuji opened this issue Feb 9, 2022 · 5 comments
Closed

Building findutils fails on macOS #17

climbfuji opened this issue Feb 9, 2022 · 5 comments
Labels
bug Something is not working

Comments

@climbfuji
Copy link
Collaborator

It looks like a recent update to spack (spack/spack#28316) breaks building findutils on my macOS, see the comment here: spack/spack#28316 (comment)

@kgerheiser
Copy link
Contributor

I get the same error.

But it attempted a longstanding problem I had with findutils. MPICH required findutils and it failed with GCC. I just removed the findutils dependency from MPICH and let it use the system one.

For whatever reason the find on macOS is not detected as external (BSD vs. GNU, I think).

@climbfuji
Copy link
Collaborator Author

I already have a PR for the authoritative spack repo, and there will be one for our fork later today (same commit, cherry-picked).

@kgerheiser
Copy link
Contributor

Any objections to changing to version 4.8.0 in the main packages.yaml? Else I would add 4.8.0 to the generic macOS site config so that it can build with GCC.

@climbfuji
Copy link
Collaborator Author

Any objections to changing to version 4.8.0 in the main packages.yaml? Else I would add 4.8.0 to the generic macOS site config so that it can build with GCC.

I think there was a problem with 4.8.0 on one of the HPCs ... because 4.7.0 worked "everywhere" (I tested) I went for that one. I think it was on Cheyenne if I remember correctly. We can make 4.8.0 the default and change it for Cheyenne or whichever the problematic machine was.

@kgerheiser kgerheiser added the bug Something is not working label Feb 11, 2022
@climbfuji
Copy link
Collaborator Author

This issue was resolved by adding a bugfix for 4.7.0 to spack (it's also in the official repo by now). We also made 4.8.0 the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

No branches or pull requests

2 participants