serac: Problem with building serac

I’m trying to build serac on my computer. I get the following Checksum error both in building developer’s tools and dependencies.

Error: ChecksumError: sha256 checksum failed for /home/saman/serac/uberenv_libs/builds/spack-stage-rz4d952n/4075.patch

and follows by

    Expected 3387faf4a71efe81c0fa17410b270ca7d352081ac88d2322df3da9bb6a6a3f2d but got 42d8b2163a2f37a745800ec13a96c08a3a20d5e67af51031e51f63313d0dedd1

/home/saman/serac/uberenv_libs/spack/lib/spack/spack/package.py:1088, in do_fetch:
       1085
       1086        self.stage.cache_local()
       1087
  >>   1088        for patch in self.spec.patches:
       1089            patch.fetch(self.stage)
       1090            if patch.cache():
       1091                patch.cache().cache_local()

anyone knows how to resolve this? Thanks.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 17 (11 by maintainers)

Most upvoted comments

You don’t have to build mfem through our suggested way but this is the way we have vetted and recommend. If you wish to do everything yourself you can just point your already built mfem to our cmake system with defining MFEM_DIR. This can be done with either ./config-build.py or running cmake directly with -DMFEM_DIR=<path/to/mfem/install>.

If you go this way you will need to define other cmake variables that are output by the serac spack package in our host-configs. You can see examples of them in host-configs/

white238 on Apr 1, 2020

@samuelpmish Yes that is correct I had the cmake problem. I did try bunch of these things and it seems to be working now! I’ll build it in my other machine (also ubuntu 18.04) again to make sure this is resolved. My question is why there is a need to pull a spack instance for serac seperately? I already have spack (for building mfem with bunch of its libraries). I have two spacks and two mfems now and so many other libraries. What am I missing here?

samanseifi on Apr 1, 2020

@samuelpmish It must have been, a long time ago 😅. spack clean replaced it indeed.

adrienbernede on Apr 1, 2020

On my machine, your error comes from trying to install cmake@3.15.5:

~/serac/uberenv_libs/spack/bin$ ./spack --version
0.13.2

~/serac/uberenv_libs/spack/bin$ ./spack stage cmake@3.15.5

==> Error: sha256 checksum failed for /tmp/sam/spack-stage/spack-stage-8ch53v5s/4075.patch
Expected 3387faf4a71efe81c0fa17410b270ca7d352081ac88d2322df3da9bb6a6a3f2d but got 42d8b2163a2f37a745800ec13a96c08a3a20d5e67af51031e51f63313d0dedd1

but after checking out a more recent version of spack (from bump_spack_version branch project.json)

~/serac/uberenv_libs/spack/bin$ git checkout 0c7fff60651

~/serac/uberenv_libs/spack/bin$ ./spack --version
0.14.1-433-0c7fff606

it can handle cmake@3.15.5 successfully

~/serac/uberenv_libs/spack/bin$ ./spack stage cmake@3.15.5
==> Fetching https://github.com/Kitware/CMake/releases/download/v3.15.5/cmake-3.15.5.tar.gz
###################################### 100.0%
###################################### 100.0%
==> Staging archive: /tmp/sam/spack-stage/spack-stage-cmake-3.15.5-6z3fks2zjax2twzuicotskwi7ylvbni5/cmake-3.15.5.tar.gz
==> Created stage in /tmp/sam/spack-stage/spack-stage-cmake-3.15.5-6z3fks2zjax2twzuicotskwi7ylvbni5

What worked for me was to delete the old version of spack, use the project.json with a more recent version and try building again.

~/serac$ rm -rf uberenv_libs/spack/

~/serac$ git checkout bump_spack_version scripts/uberenv/project.json

~/serac$ python3 scripts/uberenv/uberenv.py

@adrienbernede ‘purge’ doesn’t seem to be a spack command, is clean the same thing?

samuelpmish on Apr 1, 2020