| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* [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.
|
|
|
|
|
|
|
|
|
|
* Emacs native compilation on master
* emacs: Mark tools correctly as build dependency
|
|
Co-authored-by: Nat Shineman <shineman.5@buckeyemail.osu.edu>
|
|
Simplify logic by just enabling or disabling fsync as user specified
(default to off currently). Also remove the 4.1 version check, since
that version isn't actually supported in here.
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
|
|
The implementation for __str__ has been simplified to traverse the spec directly,
and doesn't call anymore the flat_dependencies method. Dead code has been
removed.
|
|
For configure (e.g. for hdf5) to pass, this option needs to be pulled out when invoked in ccld mode.
I thought it had fixed the issue but I still saw it after that. After some digging, my guess is that I was able
to get hdf5 to build with ifort instead of ifx. Lot of overlapping changes occurring at the time, as it were.
There are still outstanding issues building hdf5 with ifx, and Intel is looking into what appears to be a
compiler bug, but this manifests during build and is likely a separate issue.
I have verified that the making the edit in 'ccld' mode removes the -loopopt=0 and enables hdf5 to pass
configure. It should be fine to make the edit in 'ld' mode as well, but I have not tested that and didn't
include an -or- condition for it.
|
|
|
|
|
|
Add the latest release.
|
|
Mac. (#23625)
|
|
hipMalloc3D,hipMallocPitch() (#23620)
|
|
Add new release of SEACAS.
Update netcdf-c version to recent release which fixes some issues that have caused problems in past
Use release version of CGNS instead of develop
|
|
There are no official releases yet, so just use a git snapshot for now.
|
|
|
|
|
|
|
|
release (#23608)
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 2.1.4 to 2.1.5.
- [Release notes](https://github.com/actions/cache/releases)
- [Commits](https://github.com/actions/cache/compare/v2.1.4...v2.1.5)
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
|
The previous version did not fix an error that only occured with clang.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Update Nalu-Wind to remove SuperLU from Trilinos requirement. Also simplify Nalu-Wind package.
* Leave boost option in nalu-wind.
* Add git branches into TPL requirements. Update OpenFAST for change to main branch.
|
|
Adds a new release version for SLATE and includes
HIP/ROCm backend support. Now can build with either
CUDA or ROCm support.
|
|
Currently, environment views blink out of existence during the view regeneration, and are slowly built back up to their new and improved state. This is not good if other processes attempt to access the view -- they can see it in an inconsistent state.
This PR fixes makes environment view updates atomic. This requires a level of indirection (via symlink, similar to nix or guix) from the view root to the underlying implementation on the filesystem.
Now, an environment view at `/path/to/foo` is a symlink to `/path/to/._foo/<hash>`, where `<hash>` is a hash of the contents of the view. We construct the view in its content-keyed hash directory, create a new symlink to this directory, and atomically replace the symlink with one to the new view.
This PR has a couple of other benefits:
* It future-proofs environment views so that we can implement rollback.
* It ensures that we don't leave users in an inconsistent state if building a new view fails for some reason.
For background:
* there is no atomic operation in posix that allows for a non-empty directory to be replaced.
* There is an atomic `renameat2` in the linux kernel starting in version 3.15, but many filesystems don't support the system call, including NFS3 and NFS4, which makes it a poor implementation choice for an HPC tool, so we use the symlink approach that others tools like nix and guix have used successfully.
|
|
|
|
* tau: depend on provider of elf
* Depends on elf when +elf, not +libdwarf
|
|
Add Ginkgo ROCmPackage support and improve tests.
|
|
Co-authored-by: Robert Mijakovic <robert.mijakovic@lxp.lu>
|
|
* Added the option to use high performance linkers: gold and lld, for
LBANN. Including them as build flags causes unnecessary propagation
to all dependent packages, reducing package reuse.
|
|
* Package gmsh making clear dependencies
* Improvements from reviewer advise
|
|
* Enhancing package ngspice to produce bin, take options
* Enhancing package ngspice, adding dependencies
* Enhancing package ngspice, typo
|
|
fixes #22351
The ASP-based solver now accounts for the presence
in the DAG of deprecated versions and tries to minimize
their number at highest priority.
|
|
|
|
This reverts and fixes commit 1ae28f66c6e53889c7f76f234a011672fefe37a4.
Co-authored-by: lukebroskop <luke.roskop@hpe.com>
|
