This project is mirrored from Pull mirroring updated .
  1. 23 Dec, 2014 1 commit
  2. 19 Dec, 2014 9 commits
  3. 18 Dec, 2014 20 commits
    • barmston's avatar
      cabal install can be used inside a cabal exec environment · 0a4aed40
      barmston authored
      Inside a cabal exec environment cabal should be configured to always use the
      correct environment. When there is a sandbox this is addressed by setting the
      CABAL_SANDBOX_CONFIG environment variable.
      However GHC is configured to use the correct package database through setting
      the GHC_PACKAGE_PATH environment variable to include the sandbox database. The
      Cabal library previously refused to operate when GHC_PACKAGE_PATH is set in
      order to avoid having a different view of the package databases to GHC.
      In the case of a cabal exec environment being loaded for a cabal sandbox, it
      is safe to allow the use of GHC_PACKAGE_PATH as it is being used to ensure
      that GHC uses the same package database as cabal does.
      A check is made that GHC_PACKAGE_PATH matches the value that cabal exec set it
      to. If it does use of GHC through cabal is permitted.
      Fixes #1800
    • tibbe's avatar
      Bump dependency on Cabal to · 93b2e257
      tibbe authored
    • tibbe's avatar
      Bump version numbers to · 82d2fe1f
      tibbe authored
    • ttuegel's avatar
      Document --enable-coverage · 40b0df95
      ttuegel authored
    • ttuegel's avatar
      PackageTests: set dist prefix · 61f97e07
      ttuegel authored
      Some package tests run multiple tests on the same package, causing the
      build directory to be overwritten. For debugging, it is important to
      keep the build directory contents, so in this case we run each test
      with a different build directory.
    • ttuegel's avatar
    • ttuegel's avatar
      Enable library profiling when profiling executables · 6b631745
      ttuegel authored
      It doesn't make any sense to do a profiling build of an executable if
      the library doesn't have a profiled build! The option
      --enable-executable-profiling is changed to --enable-profiling to
      reflect that it is now a global flag. The old option is still recognized
      (for now).
    • ttuegel's avatar
      Build shared library when linking executables dynamically · 2976fef4
      ttuegel authored
      Dynamically linking executables will fail without a shared library
      unless the executables do not depend on the library or there is no
      library. If there is no library, building shared libraries comes at no
      cost. If there is a library, the executables usually depend on it, so it
      makes sense to --enable-shared.
      If the user passes --disable-shared, it will still be honored, but a
      warning will be produced.
    • ttuegel's avatar
      PackageTests: add full range of TestSuite/Hpc tests · 6af70b39
      ttuegel authored
      Also runs the HPC tests regardless of the detected version.
    • tibbe's avatar
      Merge branch 'master' of · ea8735aa
      tibbe authored
    • tibbe's avatar
    • Herbert Valerio Riedel's avatar
      Add 'binary' to bootstrap packages · baefd55a
      Herbert Valerio Riedel authored
      This needed since Cabal requires `binary == 0.7.*` which is only
      satisfied by GHC 7.8 and later.
      With this, now should work for (at least) GHC 7.4 and later
    • Herbert Valerio Riedel's avatar
    • tibbe's avatar
      Merge branch 'master' of · 64761550
      tibbe authored
    • tibbe's avatar
    • Andres Löh's avatar
      Improve solver error messages slightly. · eb9dcd4e
      Andres Löh authored
      As a consequence of treating all flag choices as a common goal for
      conflict set computation, error message slicing was broken and did
      not contain any information about flag choices anymore.
      With this change, information about flag choices is once again
      included in error messages.
    • Andres Löh's avatar
      Fix handling of manual flags. · ca4f58d8
      Andres Löh authored
      This hopefully addresses issue #2280.
      The problem was as follows: In the modular solver, manual flags are
      enforced. However, in order to respect manual choices by the user,
      which are still allowed, we would first check if one of the two choices
      had already been disabled, and only if that's not the case, disable
      the non-default choice.
      However, a manual user constraint is not the only reason why the default
      flag choice can be disabled at this point. It can already be disabled
      in the validation phase, if it's immediately obvious to the solver at
      this point that it can never work. In such a situation (which is
      described in #2280), the solver would then fail to respect a manual
      flag and allow to change it without user intervention.
      The fix seems simple: we now explicitly check whether the flag choice
      has been disabled *by the user*, and only then leave it alone.
      Otherwise, we enforce the manual flag.
    • Luite Stegeman's avatar
    • Luite Stegeman's avatar
      Move parts of Distribution.Simple.GHC that can be shared with other · 40ee6191
      Luite Stegeman authored
      GHC-derived compiler flavors to Distribution.Simple.GHC.Internal
    • Luite Stegeman's avatar
      Read `setup-config' into a strict ByteString, making sure that the · f958e32e
      Luite Stegeman authored
      file handle does not stay open.
      This caused permission denied problems on MSYS where the working
      temp directory could not be removed after building a package because
      of a lingering open file.
      Additionally, I've uglified the qualifier for the import of
      Data.ByteString.Lazy.Char8, since it's ugly and potentially risky,
      and should be clearly visible as such.
  4. 16 Dec, 2014 3 commits
  5. 15 Dec, 2014 1 commit
  6. 12 Dec, 2014 6 commits