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

mkl: add scalapack libraries to output #73227

Merged
merged 1 commit into from Nov 18, 2019
Merged

Conversation

markuskowa
Copy link
Member

Motivation for this change

Add the scalapack extensions to the output.

Things done

Tested compilation with an external program (bagel quantum chemistry). Seems to work fine.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @bhipple

Copy link
Member

@smaret smaret left a comment

Choose a reason for hiding this comment

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

On Darwin we unpack and install all the libraries from the MKL. Perhaps we should do the same for NixOS/Linux?

@markuskowa
Copy link
Member Author

@smaret Not sure it would make sense to unpack all RPMs. There is a lot of stuff that is distributed of a bunch directories that may not be required. @bhipple may be able to give more insight here.

Copy link
Contributor

@bhipple bhipple left a comment

Choose a reason for hiding this comment

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

I think having a whitelist of RPMs to include -- as we're currently doing -- is preferable to including everything. It's relatively easy to add more if people need it, and there are many packages unlikely to be used.

I might :sort the list though.

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.

None yet

3 participants