Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jan 18, 2015
  1. Ryan Scott

    Fix "ambigious" typos

    RyanGlScott authored
  2. Thomas Tuegel Johan Tibell

    Fix backward compat option --enable-library-coverage

    ttuegel authored tibbe committed
    (cherry picked from commit 66dade3)
  3. Thomas Tuegel Johan Tibell

    Add --enable-executable-profiling for backward compat

    ttuegel authored tibbe committed
    (cherry picked from commit f445c3a)
Commits on Jan 9, 2015
  1. Brent Yorgey
  2. Brent Yorgey
  3. Brent Yorgey
Commits on Jan 3, 2015
  1. Johan Tibell

    Add support for emitting debug info

    tibbe authored
    If the compiler (e.g. GHC 7.10) supports outputting OS native debug
    info (e.g. DWARF) passing --enable-debug-info[=n] to cabal will
    instruct it to do so.
Commits on Dec 23, 2014
  1. Mikhail Glushenkov

    -Wall police.

    23Skidoo authored
  2. Luite Stegeman

    Do not fail when the setup executable does not exist when checking

    luite authored
    for the windows clean hack.
    This would cause exceptions when using a cached setup executable,
    making parallel builds on Windows completely unusable.
Commits on Dec 19, 2014
  1. Johan Tibell
  2. Christiaan Baaij

    Always setup (DY)LD_LIBRARY_PATH for testsuite

    christiaanb authored
    Now that Cabal is in charge of RPATH handling on certain OS',
    we must always setup a correct (DY)LD_LIBRARY_PATH when
    running the testsuite. Not just when we are building relocatable
    The "problem" is, is that Cabal now adds an RPATH pointing
    to the installation location of the library. However, during
    testing, the library won't be there yet. We much hence setup
    a (DY)LD_LIBRARY_PATH that includes the dist/build dir.
Commits on Dec 18, 2014
  1. Ben Armston

    cabal install can be used inside a cabal exec environment

    benarmston 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
  2. Johan Tibell

    Merge branch 'master' of

    tibbe authored
  3. Johan Tibell
  4. Johan Tibell
  5. Andres Löh

    Improve solver error messages slightly.

    kosmikus 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.
  6. Andres Löh

    Fix handling of manual flags.

    kosmikus 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.
  7. Luite Stegeman
Commits on Dec 15, 2014
  1. lspitzner

    commandline-documentation: mention `sandbox` command again

    lspitzner authored
    (mistakenly got removed when restructuring)
Commits on Dec 12, 2014
  1. Christiaan Baaij
  2. Christiaan Baaij
  3. Christiaan Baaij
  4. Christiaan Baaij
  5. Christiaan Baaij
  6. Christiaan Baaij
  7. Christiaan Baaij
  8. Christiaan Baaij
  9. Christiaan Baaij
Commits on Dec 10, 2014
  1. Luite Stegeman

    use CompilerInfo rather than CompilerId for resolving flags and

    luite authored
    path templates.
    CompilerInfo contains more information about the compiler than
    CompilerId, which just stores the flavour and version. In particular,
    CompilerInfo knows an AbiTag, which can be used to tell binary
    incompatible results from the same compiler apart, and detailed
    information about supported languages and extensions.
    Some fields in CompilerInfo may be left unknown (Nothing). This can
    be used in the future to allow partially resolving configurations
    based on supported languages or extensions.
Commits on Dec 7, 2014
  1. lspitzner
  2. lspitzner

    Change globalCommands description generation

    lspitzner authored
    - previously, runCommands internally modified the description
      by adding the list of commands.
    - now, globalCommands is a function that builds the complete
      description without need for changes during runCommands invocation.
    - slightly more code duplication, but better separation of concerns
  3. lspitzner

    Merge branch 'master' into documentation

    lspitzner authored
  4. lspitzner
  5. lspitzner
  6. lspitzner
Something went wrong with that request. Please try again.