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

[JOSS] Spack build failing #132

Closed
jakelangham opened this issue Aug 24, 2024 · 2 comments
Closed

[JOSS] Spack build failing #132

jakelangham opened this issue Aug 24, 2024 · 2 comments

Comments

@jakelangham
Copy link

This issue relates to the ongoing reviews at openjournals/joss-reviews#7018.

I was able to successfully build discotec via spack on two machines (a desktop and HPC).

However, on another cluster, the build fails to build one of the dependencies (libevent-2.1.12) because spack can't find openssl/ssl.h. This certainly isn't discotec's fault (it turns out that header is in a slightly odd place on that system), but ultimately it does affect the installation process. Therefore, perhaps for users like me that are unfamiliar with spack, you could add a brief bit of guidance to the README about how to get spack look for things in the right places. After all, it's pretty common when building on HPC to have to do this kind of troubleshooting. (This may also be helpful for the CMake installation option too, though people are probably more familiar with CMake in general.)

@freifrauvonbleifrei
Copy link
Contributor

the Spack installation is getting a bit more space in the new documentation: https://discotec.readthedocs.io/en/latest/getting_started.html , including links to the typical Spack resources. @jakelangham do you think you would know where to look based on this info? Unfortunately, resolving dependencies on HPC can be very complex, which is why we (and many HPC operators) try to outsource as much as possible to Spack and its documentation.

@jakelangham
Copy link
Author

I think the new documentation is sufficient to close this.

I got the code built on all 3 systems in the end with spack and cmake, so that feels like a decent test of the install process. FYI, I actually didn't find the spack documentation all that useful in this regard, since it seems more aimed at package developers and sysadmins than impatient users who just want to build 1 piece of software. But that is hardly your responsibility!

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

No branches or pull requests

2 participants