Can we make errors like missing -dev libraries more obvious? #1152

Open
nh2 opened this Issue Dec 15, 2012 · 2 comments

Comments

Projects
None yet
5 participants
Contributor

nh2 commented Dec 15, 2012

Regularly when I install packages with many dependencies, I get something like this:

checking for OpenAL/alc.h... no
configure: error: in `/tmp/OpenAL-1.4.0.1-20242/OpenAL-1.4.0.1':
configure: error: no OpenAL headers found, so this package cannot be built
See `config.log' for more details
Failed to install OpenAL-1.4.0.1
Downloading gloss-1.7.6.5...
...
Updating documentation index /home/niklas/.cabal/share/doc/index.html
cabal: Error: some packages failed to install:
ALUT-2.2.0.0 depends on OpenAL-1.4.0.1 which failed to install.
OpenAL-1.4.0.1 failed during the configure step. The exception was:
ExitFailure 1
edge-0.8.16 depends on OpenAL-1.4.0.1 which failed to install.

Here, the installation of a package failed due to missing openal-dev libraries; after that, cabal continues to install other packages, which is good.

The problem is that at the end, I mainly see

OpenAL-1.4.0.1 failed during the configure step. The exception was:
ExitFailure 1

Which is not very informative. I have to scroll up through all of the cabal output, looking for something that looks like an error.

Could we make finding the location of the error easier? I am thinking of

  • Showing the errorneous command and its output again at the end
  • Writing a log file to ~/.cabal and mentioning it at the end of a failed cabal install
  • Using colours (that might be useful in general).
Member

23Skidoo commented Dec 15, 2012

Previously discussed here (in the context of parallel install). I plan to revisit this when I'll get around to implementing #975.

23Skidoo was assigned Dec 31, 2012

23Skidoo added the enhancement label Mar 8, 2014

ntc2 commented Jan 29, 2016

There's a duplicate with more subscribers here: #2580

@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016

23Skidoo removed their assignment Sep 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment