Closed
Conversation
* nyancat: adding the most important piece of software ever written * nyancat: some formatting updates * nyancat: flake8 error fix
* Also add missing zlib dependency
* LIBXSMM 1.10 * Accurately replaced MD5 with SHA256 sums (libxsmm).
Needed to compile with gcc@8 and recent versions of glibc.
glib should not use the globally installed gtk-doc. Otherwise, gtk-doc can fail with Python errors such as `ImportError: No module named site`. This is due to the fact that Spack sets `PYTHONHOME`, which can confuse the global Python installation that is used by gtk-doc.
* r-combinat: new package at 0.0-8 * r-combinat: add list_url
* Add pic variant to cflags in boost. * Improve description in pic variant of boost, see spack#9750.
* trinotate: fix perl location * trinotate: not where that is * trinotate: glob * trinotate: needs perl-dbd-sqlite
* intel-parallel-studio: add missing updates * add 2018.4
* use AutotoolsPackage so config.guess get updated by autoreconf step, fix build problem on ppc spack#9673 * same error, same fix under ppc arch
* erne: new package starting at 2.1.1 * erne: remove unused configure args * erne: remove unused prefix arg * erne: add explicit mpi disable
- Add 1.85 - OPENSSL_PREFIX has to be set in the environment, otherwise Spack's openssl will not be found
Required for [email protected] compatibility.
Libunwind releases are few and far between, so we need access to recent snapshots from the git repository. Pass cflags to configure so that make will respect the value from the spack install line.
Pass cflags to configure so that configure gets the values from the spack install line. Disable -Werror so that we don't fail the build over a stray warning.
* mark: Create new package. * mark: change description. * mark: change description. * mark: Delete set_up environment. * mark: replace join_path(prefix.bin, mark) with prefix.bin.mark
…#8986) * zoltan: only add gussed MPI libs if no MPI wrappers are used - if MPI-wrappers are used for compilation, we can assume that linking works without manually specifying MPI libs (guessing may result in wrong libs, cf. spack#8979) - thus, only guess the NPI libs and add them explicitly if no MPI-wrappers are used - use llnl.util.filesystem.find_libraries instead of a locally defined routine to guess the MPI libs if needed (cf. spack#8979) * zoltan: rely on MPI-wrappers to know the required MPI libs
* GDL: python integration fixes * renamed python-related variants to follow the convention * building the Python module requires patches currently targetting 0.9.8 othwerwise asking for the Python module *only* builds the Pyhton module * building the python module also requires patching the vendored (with the GDL) antlr to be built as a shared library * Typo Co-Authored-By: rmsds <[email protected]> * Rename embed-python variant to embed_python
* SEACAS: Add preliminary support for seacas package * Eliminate leftover from package I copied from. * And remove another stray line Sorry, thought I had checked this better... * SEACAS: Shorten long lines; fixup indentation * SEACAS: Remove unused os import * Add PLASMA version 18.11.0 and Lua variant (spack#9689) * Add PLASMA 18.11.1 with optional Lua and test for headers * New versions for a few python modules (spack#9969) * py-jupyter-console: Add version 5.2.0 * py-jupyter-core: add version 4.4.0 * py-lxml: add version 4.2.5 * py-zmq: add version 17.1.2 * py-terminado: add version 0.8.1 * py-pexpect: add version 4.6.0 * py-pytables: add version 3.4.4 * SEACAS: Default to mpi on * SEACAS: Modify to reduce variants Instead of using an `allpkgs` or explicitly specifying each individual subset, changed to minimize variants: * By default, the exodus and IOSS libraries are built and a few executables directly related to the IOSS library. * variant `common` defaults to True and builds the "common" seacas applications. This is based on my definition, so there may be could be some discussion on what belongs here. * variant `legacy` defaults to True and builds the remainder of the seacas applications. These are still used, but mainly in more esoteric areas. Might be better to default to False, but I wanted default to just build everything which is what other SEACAS builds always do... Removed the `kokkos` variants for now as I need to do some more thinking on how best to support this. Not often used currently, so shouldn't be an issue. Cleaned up other issues raised by Adam and found by me. * SEACAS: Address flake8 issues * SEACAS: Clean up variant package logic Fixed package variant logic. Consolidated some other variant handling logic Other minor refactors for hopefully better readability * SEACAS: Fix flake8 error Missing whitespace around operator fixed.
- previous removal of FOAM_EXT_LIBBIN (ThirdParty) from the environment during the build could lead to the system scotch library being found instead of the spack installation. Avoid this largely cosmetic change to the setting in favour of improved build robustness. These modifications will be largely superfluous in the 1812 release anyhow. - Split the patching algorithm into 'regular' and '@:1806' since the next versions of openfoam will again need fewer patches. - Add hook into foamCreateManpage to be used where available
* Add patch to fix windows.h include in freetype * Fix patch
* Update Spack's Bash completion script * spack mirror create options changed
This reverts commit 90b34c9.
* Added rocksdb package * Fixes based on @tristan0x and @pramodk comments * Cleanup * A couple minor fixes based on @adamjstewart 's advice * Fixed flake8 errors
* Add spack package for saga-gis * Adjusted license header * Adjust saga-gis package, added fixme comments * Removed version constraint * Fixed fixme comment
* Add thread count variant Atlas automatically configures itself and optimizes to run with a fixed number of threads. This can be overridden during compile by setting a flag and atlas will tune itself to use the specified number, rather than all system CPUs. Default value is the existing logic, autoconfigure. * Fix Linting * Another lint for longline
spack#9933) When this variant is set, it requires boost to be built with the +pic variant.
* clp: add build_directory, remove old hack * clp: use spack-build for building
Also unpin the version from the arrow package.
Conflicts: lib/spack/spack/cmd/env.py lib/spack/spack/environment.py lib/spack/spack/schema/config.py lib/spack/spack/test/conftest.py lib/spack/spack/test/environment_modifications.py lib/spack/spack/util/environment.py var/spack/repos/builtin/packages/sqlite/package.py
marcmengel
pushed a commit
that referenced
this pull request
Apr 21, 2023
1. support version 3.1.3, which now depends on sundials@6 2. support version 3.1.2:, which broke the two patch files and therefore the two patch files have been replaced by more flexible filter_file() commands inside a patch() function. 3. rename the variant for python extension from using the package name "+pyuqtk" to the more standard "+python" 4. add maintainers @omsai and the upstream developer @bjdebus who offered to help with the spack packaging. 5. swig should only be a build-time dependency. swig is only necessary until @:3.1.0 6. confirmed python dependencies are correct by inspecting imports, subset python dependencies type to build, run, and confirmed all 31 build-time tests pass including the 9 python tests: ```console $ spack env create uqtk-dev $ spack add [email protected] $ spack install --test root && cat $(spack location -i uqtk)/.spack/install-time-test-log.txt ==> Testing package uqtk-3.1.3-nok6fut ==> [2023-04-19-14:56:25.005361] Running build-time tests ==> [2023-04-19-14:56:25.005536] RUN-TESTS: build-time tests [check] ==> [2023-04-19-14:56:25.009543] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'test' ==> [2023-04-19-14:56:25.014903] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' 'test' Running tests... /home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/cmake-3.26.3-zjmsfz23j5l4ytniz26uzvxonlu5qebr/bin/ctest --force-new-ctest-process Test project /tmp/omsai/spack-stage/spack-stage-uqtk-3.1.3-nok6fut47h42cnaau7wkoohgqy5f2qqa/spack-build-nok6fut Start 1: ArrayReadAndWrite Start 2: ArrayDelColumn Start 3: Array1DMiscTest Start 4: Array2DMiscTest 1/31 Test #1: ArrayReadAndWrite ................ Passed 0.01 sec Start 5: ArraySortTest 2/31 Test #2: ArrayDelColumn ................... Passed 0.01 sec Start 6: MultiIndexTest 3/31 Test #3: Array1DMiscTest .................. Passed 0.01 sec Start 7: CorrTest 4/31 Test #4: Array2DMiscTest .................. Passed 0.01 sec Start 8: QuadLUTest 5/31 Test #5: ArraySortTest .................... Passed 0.02 sec Start 9: MCMC2dTest 6/31 Test #6: MultiIndexTest ................... Passed 0.01 sec Start 10: MCMCRandomTest 7/31 Test #8: QuadLUTest ....................... Passed 0.02 sec Start 11: MCMCNestedTest 8/31 Test #10: MCMCRandomTest ................... Passed 0.02 sec Start 12: Deriv1dTest 9/31 Test #12: Deriv1dTest ...................... Passed 0.01 sec Start 13: SecondDeriv1dTest 10/31 Test #13: SecondDeriv1dTest ................ Passed 0.01 sec Start 14: GradHessianTest 11/31 Test #11: MCMCNestedTest ................... Passed 0.03 sec Start 15: GradientPCETest 12/31 Test #14: GradHessianTest .................. Passed 0.01 sec Start 16: PCE1dTest 13/31 Test #15: GradientPCETest .................. Passed 0.01 sec Start 17: PCEImplTest 14/31 Test #16: PCE1dTest ........................ Passed 0.01 sec Start 18: PCELogTest 15/31 Test #18: PCELogTest ....................... Passed 0.01 sec Start 19: Hessian2dTest 16/31 Test #19: Hessian2dTest .................... Passed 0.01 sec Start 20: BCS1dTest 17/31 Test #20: BCS1dTest ........................ Passed 0.01 sec Start 21: BCS2dTest 18/31 Test #21: BCS2dTest ........................ Passed 0.01 sec Start 22: LowRankRegrTest 19/31 Test #22: LowRankRegrTest .................. Passed 0.01 sec Start 23: PyModTest 20/31 Test #17: PCEImplTest ...................... Passed 0.07 sec Start 24: PyArrayTest 21/31 Test #23: PyModTest ........................ Passed 0.08 sec Start 25: PyArrayTest2 22/31 Test #25: PyArrayTest2 ..................... Passed 0.30 sec Start 26: PyQuadTest 23/31 Test #24: PyArrayTest ...................... Passed 1.44 sec Start 27: PyBCSTest1D 24/31 Test #26: PyQuadTest ....................... Passed 1.68 sec Start 28: PyBCSTest2D 25/31 Test #27: PyBCSTest1D ...................... Passed 1.66 sec Start 29: PyBADPTest 26/31 Test #7: CorrTest ......................... Passed 3.43 sec Start 30: PyRegressionTest 27/31 Test #28: PyBCSTest2D ...................... Passed 1.50 sec Start 31: PyGalerkinTest 28/31 Test #9: MCMC2dTest ....................... Passed 3.90 sec 29/31 Test #29: PyBADPTest ....................... Passed 1.66 sec 30/31 Test #30: PyRegressionTest ................. Passed 1.72 sec 31/31 Test #31: PyGalerkinTest ................... Passed 1.63 sec 100% tests passed, 0 tests failed out of 31 Total Test time (real) = 5.35 sec ==> [2023-04-19-14:56:30.382797] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'check' ==> [2023-04-19-14:56:30.385983] Target 'check' not found in Makefile ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.