Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Add framework to provide ad-hoc diagnostics for common failures #670

Closed
bos opened this Issue May 24, 2012 · 1 comment

Comments

Projects
None yet
3 participants
Contributor

bos commented May 24, 2012

(Imported from Trac #678, reported by @dcoutts on 2010-05-03)

Just as we have a system for doing various QA checks on cabal packages, perhaps we should have something to help users diagnose common problems with the system environment that crop up as e.g. linker errors.

For example, a user reported in #haskell that the wx package failed to configure and reported that the stdc++ C library was missing. We eventually discovered that although the standard C++ library was installed, it was not found by gcc -lstdc++. Installing the C++ components of gcc (ie the distro package that provides g++) fixed the issue, presumably because installing that package modified the standard gcc linker search path to include the location where stdc++ was already installed.

It would be good if after diagnosing this particular issue, it was easy to code up a test for this situation and add it into Cabal's Simple build system so that other users might get more helpful diagnostics in future. It does not need to be comprehensive, so it is ok to try and grok the output of linkers and to work just on some OSs or just with gcc for example.

This might also help with common ghc problems.

jsl commented Feb 24, 2015

Since there is no activity on this ticket since 2010 I propose closing. Please re-open or create another issue if this is still something that should be addressed.

/cc @tibbe

@tibbe tibbe closed this Feb 24, 2015

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