1. 31 Mar, 2016 1 commit
  2. 30 Mar, 2016 12 commits
  3. 29 Mar, 2016 23 commits
  4. 28 Mar, 2016 4 commits
    • Herbert Valerio Riedel's avatar
      Remove obsolete --with-hc flag from ./configure · cd3fbff9
      Herbert Valerio Riedel authored
      This was probably missed during the big build-system refactoring in
      34cc75e1
      cd3fbff9
    • Herbert Valerio Riedel's avatar
      Update bytestring submodule to latest snapshot · eb25381d
      Herbert Valerio Riedel authored
      Most notably, this pulls in the following changes
      
      > Fix breakByte and spanByte rewrite rules
      > Implement `stripPrefix`/`stripSuffix`
      
      The first patch is related to #11688
      eb25381d
    • kaiha's avatar
      Do not test for existence of the executable · 49b9d80a
      kaiha authored
      Summary:
      The test for the existence of the executable breaks on MS Windows. It is
      furthermore needless, because if the test can be executed the executable
      is obviously there.
      
      Reviewers: austin, bgamari, Phyx
      
      Reviewed By: Phyx
      
      Subscribers: Phyx, thomie
      
      Differential Revision: https://phabricator.haskell.org/D2050
      
      GHC Trac Issues: #4114
      49b9d80a
    • Herbert Valerio Riedel's avatar
      Autoconf: detect and set CFLAGS/CPPFLAGS needed for C99 mode · afc48f89
      Herbert Valerio Riedel authored
      This is the first phase of addressing #11757 which aims to make C99
      support a base-line requirement for GHC and clean up the code-base to
      use C99 facilities when sensible.
      
      This patch exploits the logic/heuristic used by `AC_PROG_CC_C99` to
      determine the flags needed in case the C compiler isn't able to compile
      C99 code in its current mode. We can't use `AC_PROG_CC_C99` directly
      though because GHC's build-system expects CC to contain a filename
      without any flags, while `AC_PROG_CC_C99` would e.g. result in
      `CC="gcc -std=gnu99"`. Morever, we support different `CC`s for
      stage0/1/2, so we need a version of `AC_PROG_CC_C99` for which we can
      specify the `CC`/`CFLAGS` variables to operate on. This is what
      `FP_SET_CFLAGS_C99` does.
      
      Note that Clang has been defaulting to C99+ for a long time, while GCC 5
      defaults to C99+ as well. So this has mostly an affect on older GCCs
      versions prior to 5.0 and possibly compilers other than GCC/Clang (which
      are not officially supported for building GHC anyway).
      
      Reviewers: kgardas, erikd, bgamari, austin
      
      Reviewed By: erikd
      
      Differential Revision: https://phabricator.haskell.org/D2045
      afc48f89