spack: Unable to add external packages built with Spack to packages.yaml

Never seen this one before. I’m trying to build something with intel-parallel-studio and I don’t want to reinstall intel-parallel-studio for every compiler, so I added it to my packages.yaml like so:

packages:
  all:
    # Set Intel as default compiler
    compiler: [intel, gcc, pgi, nag]
    providers:
      # Set Intel MKL as default BLAS/LAPACK
      blas:   [intel-parallel-studio]
      lapack: [intel-parallel-studio]
      # Set MVAPICH2 as default MPI
      mpi: [mvapich2, mpich, openmpi]
    variants: ~mpi+openmp
  intel-parallel-studio:
    paths:
      intel-parallel-studio@professional.2017.2+all+daal~ilp64+ipp+mkl+mpi~newdtags~openmp+rpath+shared+tools arch=linux-rhel7-x86_64: /data/software/spack/opt/spack/linux-rhel7-x86_64/gcc-4.8.5/intel-parallel-studio-professional.2017.2-2btuqpiiqgrqbmnmxxe7jletuqppyktc
    buildable: False

But when I try to build hpl, I see:

$ spack install hpl
==> Installing hpl
==> mvapich2 is already installed in /data/software/spack/opt/spack/linux-rhel7-x86_64/intel-17.0.2/mvapich2-2.2-bn3h2ts3ncoizpmyebhq6ofdvrobq57i
==> intel-parallel-studio is externally installed in /data/software/spack/opt/spack/linux-rhel7-x86_64/gcc-4.8.5/intel-parallel-studio-professional.2017.2-2btuqpiiqgrqbmnmxxe7jletuqppyktc
==> Error: AssertionError: 
/data/software/spack/lib/spack/spack/build_environment.py:569, in child_execution:
     549      def child_execution(child_connection, input_stream):
     550          try:
     551              setup_package(pkg, dirty=dirty)
     552              function(input_stream)
     553              child_connection.send(None)
     554          except StopIteration as e:
     555              # StopIteration is used to stop installations
     556              # before the final stage, mainly for debug purposes
     557              tty.msg(e.message)
     558              child_connection.send(None)
     559          except:
     560              # catch ANYTHING that goes wrong in the child process
     561              exc_type, exc, tb = sys.exc_info()
     562  
     563              # Need to unwind the traceback in the child because traceback
     564              # objects can't be sent to the parent.
     565              tb_string = traceback.format_exc()
     566  
     567              # build up some context from the offending package so we can
     568              # show that, too.
  >> 569              package_context = get_package_context(tb)
     570  
     571              build_log = None
     572              if hasattr(pkg, 'log_path'):
     573                  build_log = pkg.log_path
     574  
     575              # make a pickleable exception to send to parent.
     576              msg = "%s: %s" % (str(exc_type.__name__), str(exc))
     577  
     578              ce = ChildError(msg, tb_string, build_log, package_context)
     579              child_connection.send(ce)
     580  
     581          finally:
     582              child_connection.close()

I have no idea what this means. Anyone else? The intel-parallel-studio installation went by fine and I’m using it to install the dependencies, so there’s nothing wrong with that.

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 17 (16 by maintainers)

Most upvoted comments

Is this still an issue? I haven’t needed to do this in a long time, so I’m fine with closing this issue unless someone else can reproduce it.

I don’t think the above analysis was very clear on my part. It appears to me that anything marked as buildable: False is unable to be used in compiling any package. I tried doing libxcb with just xcp-proto in my packages.yaml, for example, and it failed as well.

I think the best / most important test case would be mpi related packages, if those are marked as buildable: False and you cannot use them to build something that uses MPI, then it seems likely that this is indeed the problem.