spack: Unable to build boost with error "Archive was empty"
After successfully installing boost 1.63.0 with GCC 5.4.0, I failed to buid it against Intel compiler 16.0.3. The erorro message says “Archive was empty for boost”. However, I am pretty sure that the boost package has been downloaded and I can unarchive it manually.
Any advice on further digging into this issue? Thank you.
$ spack install boost %intel@16.0.3
==> Installing boost
==> bzip2 is already installed in /lustre/spack/sandybridge/linux-centos7-x86_64/intel-16.0.3/bzip2-1.0.6-qz2i6vx23esuzvr3jntzoavyewf5aucw
==> zlib is already installed in /lustre/spack/sandybridge/linux-centos7-x86_64/intel-16.0.3/zlib-1.2.10-exoivhx3ti4qedcevvrr6bcv7s7mjz5c
==> Fetching http://downloads.sourceforge.net/project/boost/boost/1.63.0/boost_1_63_0.tar.bz2
######################################################################## 100.0%
==> Already staged boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h in /home/rpm/spack/var/spack/stage/boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h
==> Error: StageError: Archive was empty for boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h
/home/rpm/spack/lib/spack/spack/package.py:965, in do_stage:
957 def do_stage(self, mirror_only=False):
958 """Unpacks the fetched tarball, then changes into the expanded tarball
959 directory."""
960 if not self.spec.concrete:
961 raise ValueError("Can only stage concrete packages.")
962
963 self.do_fetch(mirror_only)
964 self.stage.expand_archive()
>> 965 self.stage.chdir_to_source()
$ ls -alh /home/rpm/spack/var/spack/stage/boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h/
total 79M
drwx------ 3 rpm rpm 80 Feb 3 23:40 .
drwxrwxr-x 3 rpm rpm 60 Feb 3 23:33 ..
-rw-rw-r-- 1 rpm rpm 79M Feb 3 23:40 boost_1_63_0.tar.bz2
drwxrwxr-x 2 rpm rpm 40 Feb 3 23:33 spack-expanded-archive
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 17 (13 by maintainers)
Commits related to this issue
- Pass empty dict as env param when expanding archives fix #3018 — committed to dalg24/spack by dalg24 9 years ago
I happed to built boost against Intel compiler several days ago. It works well.
@dalg24 could you add
--restageflag and try it again?This error appears to occur before the build, when Spack is attempting to unpack the source. I’m curious if things succeed when you do:
spack clean boostand retry the install. What seems odd to me is that spack fetched boost as though it had never been downloaded before, but the staging directory had already been created:
==> Already staged boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h in /home/rpm/spack/var/spack/stage/boost-1.63.0-dlne5jb6p33roxb3bn5edke4a3ya6b2h