This project is mirrored from Pull mirroring updated .
  1. 13 Dec, 2015 2 commits
    • Herbert Valerio Riedel's avatar
      Use standard mechanism to tell ./configure the c-compiler · 47259753
      Herbert Valerio Riedel authored
      Most Autoconf configure scripts don't support the non-standard `--with-gcc`
      flag, and there does not seem to be any good reason to do so, since
      Autoconf has already a proper way to set the c-compiler:
      Either via the `CC` environment variable, or (with higher precedence)
      by passing a commandline argument of the form `CC=clang-3.8`.
      This patch simply replaces the previous non-standard `--with-gcc=clang-3.8`
      argument (which was clearly misnamed to begin with) by a `CC=clang-3.8`
      command-line argument to the `configure` script.
    • bardur.arantsson's avatar
      Merge pull request #2943 from martinvlk/fix#1360 · 6b438148
      bardur.arantsson authored
      Implement better error handling for "sandbox delete-source"
  2. 09 Dec, 2015 1 commit
  3. 07 Dec, 2015 2 commits
  4. 06 Dec, 2015 1 commit
  5. 01 Dec, 2015 4 commits
  6. 27 Nov, 2015 4 commits
  7. 26 Nov, 2015 6 commits
  8. 25 Nov, 2015 2 commits
    • Danny Navarro's avatar
      Add solver tests for language extensions and flavours · 1f40772a
      Danny Navarro authored
      This also includes modifications to the solver testing DSL and the
      testing functions.
      This is necessary for merging PR #2732.
    • Andres Löh's avatar
      Track language extensions and language flavours in the solver. · fd5e0c65
      Andres Löh authored
      Every package now "depends" on all language extensions
      (default-extensions and other-extensions) and language flavours
      (default-language and other-languages) it declares in its cabal file.
      During solving, we verify that the compiler we use actually
      supports selected extensions and languages. This has to be done
      during solving, because flag choices can influence the declared
      extensions and languages being used.
      There currently is no equivalent check performed on the generated
      install plans. In general, cabal-install performs a sanity check
      on the solver output, checking that the solver e.g. indeed includes
      all the declared dependencies of a package. There is no such
      double-checking for language extensions. This is not really
      problematic, as all that this change does is to make the solver
      more conservative rather than less. However, having a sanity check
      available might ultimately be nice to have.
  9. 24 Nov, 2015 2 commits
  10. 23 Nov, 2015 2 commits
  11. 21 Nov, 2015 2 commits
  12. 20 Nov, 2015 2 commits
  13. 19 Nov, 2015 2 commits
  14. 17 Nov, 2015 5 commits
  15. 16 Nov, 2015 3 commits