| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This commit updates the UnifyFS package.py script to include a patch
that fixes the build problems on new-ish Linux distributions.
Fixes issue #23292
|
|
Change-Id: I3424409f8a7575c6a13592c05e1e940f960fe8fe
|
|
|
|
Change-Id: I538d72eb97d3cc91e2e6854b40c5b91b39df6f62
|
|
Change-Id: I56de34bace2fb04156700ffd4f1b34408920d702
|
|
Change-Id: I4acb232e171ddec688eb7871da80caaa05bf637b
|
|
Change-Id: I5846415b4953a5f12f995672e586cadb80857db2
|
|
Change-Id: I2c07e75b404ec289feebdbfb09f6b0e733404911
|
|
Pass -ef to the cce fortran compiler, fix the build system to use the correct openmp flag for CCE
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
Change-Id: I31a22fa1495cc2ceed33ba7084831c11120c03e7
|
|
|
|
Use the gold linker for CCE (this may change later)
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
|
|
Change-Id: I7e790014fd448eb203a1963c90e22afde041ba50
|
|
Allow for multiple definitions at link time (for CrayPE)
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
|
|
Expand the use of cray_secas.patch and use the gold linker w/cce
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
turn off static linking, add -ldl flag
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
This reverts commit cefbe48c89209dc3df654795644973b1885cdea4.
|
|
This also adds a patch to make libfuse compile with gcc@11:
|
|
* add scorec feature to trilinos recipe
* used func to enable SCOREC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This also changes the checksum for 1.22.1 because I switched the package
to use the proper upstream tarballs to get rid of the autotools
dependencies. Moreover, a few dependencies were missing. netdata also
requires a few directories to be created in its prefix to actually work.
|
|
Also adjust the libxc constraints.
|
|
Spack doesn't require users to manually index their repos; it reindexes the indexes automatically when things change. To determine when to do this, it has to `stat()` all package files in each repository to make sure that indexes up to date with packages. We currently index virtual providers, patches by sha256, and tags on packages.
When this was originally implemented, we ran the checker all the time, at startup, but that was slow (see #7587). But we didn't go far enough -- it still consults the checker and does all the stat operations just to see if a package exists (`Repo.exists()`). That might've been a wash in 2018, but as the number of packages has grown, it's gotten slower -- checking 5k packages is expensive and users see this for small operations. It's a win now to make `Repo.exists()` check files directly.
**Fix:**
This PR does a number of things to speed up `spack load`, `spack info`, and other commands:
- [x] Make `Repo.exists()` check files directly again with `os.path.exists()` (this is the big one)
- [x] Refactor `Spec.satisfies()` so that a checking for virtual packages only happens if needed
(avoids some calls to exists())
- [x] Avoid calling `Repo.exists(spec)` in `Repo.get()`. `Repo.get()` will ultimately try to load
a `package.py` file anyway; we can let the failure to load it indicate that the package doesn't
exist, and avoid another call to exists().
- [x] Fix up some comments in spec parsing
- [x] Call `UnknownPackageError` more consistently in `repo.py`
|
|
|
|
|
|
- [x] `analyze` isn't commonly used; move it to long help
(`spack -H` vs `spack -h`). Give it its own section.
- [x] make it clear from `spack -h` that `spack module` can generate
module files
- [x] shorten help for `spack style`
|
|
* do not sort projections alphabetically
* add assertion for ordered dict
|
|
|
|
* [py-pygetwindow] created template
* [py-pygetwindow] added dependencies
* [py-pygetwindow] Final cleanup
- added homepage
- added description
- removed fixmes
|
|
* [py-pyrect] created template
* [py-pyrect] depends on setuptools
* [py-pyrect] Final cleanup
- added homepage
- added description
- removed fixmes
|
|
* [py-word2number] created template
* [py-word2number] requires setuptools
* [py-word2number] Final cleanup
- added homepage
- added long description
- removed fixmes
|
|
* [py-pymsgbox] created template
* [py-pymsgbox] depends on setuptools
* [py-pymsgbox] Final cleanup
- added homepage
- added description
- removed fixmes
|
|
* [py-pytweening] created template
* [py-pytweening] depends on setuptools
* [py-pytweening] final cleanup
- added homepage
- added description
- removed fixmes
|
|
|
|
|
|
Currently, module configurations are inconsistent because modulefiles are generated with the configs for the active environment, but are shared among all environments (and spack outside any environment).
This PR fixes that by allowing Spack environments (or other spack config scopes) to define additional sets of modules to generate. Each set of modules can enable either lmod or tcl modules, and contains all of the previously available module configuration. The user defines the name of each module set -- the set configured in Spack by default is named "default", and is the one returned by module manipulation commands in the absence of user intervention.
As part of this change, the module roots configuration moved from the `config` section to inside each module configuration.
Additionally, it adds a feature that the modulefiles for an environment can be configured to be relative to an environment view rather than the underlying prefix. This will not be enabled by default, as it should only be enabled within an environment and for non-default views constructed with separate projections per-spec.
TODO:
- [x] code changes to support multiple module sets
- [x] code changes to support modules relative to a view
- [x] Tests for multiple module configurations
- [x] Tests for modules relative to a view
- [x] Backwards compatibility for module roots from config section
- [x] Backwards compatibility for default module set without the name specified
- [x] Tests for backwards compatibility
|
|
|
|
It seems that building unreleased versions requires makeinfo, which is
part of texinfo.
|
|
|
|
|
|
|
|
|
