* py-tensorflow: patch for v2.15 build errors with new compilers
* py-tensorflow: patch for v2.15 build errors with new compilers
* py-tensorflow: fix clang build and add clang version constraints
* py-tensorflow: use compiler wrapper
* py-tensorflow: relax clang conflict
* nim: fix build with new compilers
* narrow condition for disabling warnings
* move flags into offending module
disables warnings also for compiling projects other than the Nim compiler when necessary
* specify different versions pthread modules
* instead patch SysThread type
* adapt patch for old Nim versions
* Specify hypothetical `:@0.19.6` for patch version constraint
* In var/spack/repos/builtin/packages/ectrans/package.py, always set cmake argument ECTRANS_HAVE_CONTIGUOUS_ISSUE to turn off problematic use of Fortran 'contiguous' keyword
* In var/spack/repos/builtin/packages/ectrans/package.py, always set cmake argument ENABLE_FINAL=OFF to turn off problematic finalization of derived data types
* Update links to issues in fckit and ectrans
* Fix wrong cmake argument for ECTRANS_HAVE_CONTIGUOUS_ISSUE in var/spack/repos/builtin/packages/ectrans/package.py
This commit adds an additional requirement to the vecmem package,
requiring the OneAPI compiler iff the `sycl` variant is turned on. This
allows us to correctly set the non-standard `SYCLCXX` environment
variable.
* likwid: Fix the perms script
The script loops over the path (which includes the prefix), but
additionally adds the prefix up front which results in duplicate paths
and a double "/" in the command like in the following one:
chown root:root /opt/csg/spack/opt/spack/linux-debian12-zen2/gcc-12.2.0/likwid-5.4.1-xfc6quebnf2kosydl3ospaeoskxnxwhn//opt/csg/spack/opt/spack/linux-debian12-zen2/gcc-12.2.0/likwid-5.4.1-xfc6quebnf2kosydl3ospaeoskxnxwhn/sbin/likwid-accessD
Additionally the path is currently not quoted which can potentially
result in word splitting for weird paths.
Signed-off-by: Christian Heusel <christian@heusel.eu>
* likwid: Make the perm scripts' name unique
Also move it into the proper binary folder as per the Filesystem
Hierarchy Standard.
Signed-off-by: Christian Heusel <christian@heusel.eu>
---------
Signed-off-by: Christian Heusel <christian@heusel.eu>
* Initial checkin of compile file for the package libgpiod, this covers versions, 1.6.3 through 2.2
* Update var/spack/repos/builtin/packages/libgpiod/package.py
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
* Update var/spack/repos/builtin/packages/libgpiod/package.py
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
* Update how version to url is manage in the x.y.0 cases based on fix by @wdconinc
* Remove redundant url at the top since it is now inside url_for_version function
---------
Co-authored-by: Wouter Deconinck <wdconinc@gmail.com>
* xios: update to v2.6
- xios: update to v2.6
- xios: patch remap earcut.hpp for missing include file
- xios: address C++11 requirement
- xios: instruct to use external boost and blitz libraries
* xios: bump revision to 2714
- Bump revision to changeset 2714
- Deprecate older versions that I can't manage to compile
- Confirm clang workaround is still needed
A directory and a symlink to it under the same relative path in a
different prefix
```
/prefix1/dir/
/prefix1/dir/file
/prefix2/dir -> /prefix1/dir/
```
are not a blocker to create a view. The view structure simply looks like
this:
```
/view/dir/
/view/dir/file
```
This should be the case independently of the order in which we visit
prefixes, so we could in principle create views order independently.
