Skip to content

provide more informative error message when package.py execs non-existent binary #30

@malcook

Description

@malcook

For instance, building bcftools is simply untar and make; there is no ./configure file in the tarball.

But the spackage developer (erhm, that is me) failed to remove the default

    configure("--prefix=%s" % prefix)

As a result,

spack install bcftools

fails with

==> Building bcftools.
Traceback (most recent call last):
  File "/n/local/sc/lib/spack/spack/build_environment.py", line 268, in fork
    function()
  File "/n/local/sc/lib/spack/spack/package.py", line 833, in real_work
    self.install(self.spec, self.prefix)
  File "/n/local/sc/var/spack/packages/bcftools/package.py", line 40, in install
    configure("--prefix=%s" % prefix)
  File "/n/local/sc/lib/spack/spack/util/executable.py", line 77, in __call__
    stdout=subprocess.PIPE if return_output else sys.stdout)
  File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1308, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Certainly 'No such file or directory' tells me something is missing. Shouldn't it be more informative and tell me WHAT is missing?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions