1. 23 Nov, 2015 1 commit
    • Ben Gamari's avatar
      build.mk.sample: Document meaning of WERROR · 02c689cd
      Ben Gamari authored
      31bcf9b6 changed the behavior of WERROR
      such that it would only apply to the stage 2 build. The reason for this
      was to avoid silly redundant imports and such breaking validation on
      different bootstrap compiler versions.
      
      Document the fact that WERROR now only applies to the stage 2 build.
      02c689cd
  2. 07 Sep, 2015 1 commit
  3. 13 Jul, 2015 1 commit
    • Thomas Miedema's avatar
      Build system: do not build stm and parallel by default · 392ff06d
      Thomas Miedema authored
      stm and parallel have an 'extra' tag in the ./packages file, so would get
      added to PACKAGES_STAGE2 by default, and subsequently build by the stage2
      compiler.
      
      With this patch, this happens only when you set BUILD_EXTRA_PKGS=YES in
      build.mk. A normal validate still builds (and tests) the 'extra'
      packages, but they are skipped for `validate --fast`. Maybe this brings
      us closer to finishing within the 50 minute Travis limit as well.
      
      We can later try to give random, primitive and vector an 'extra' tag as
      well (now they have a 'dph' tag), but some tests will probably fail at
      first.
      
      Differential Revision: https://phabricator.haskell.org/D1065
      392ff06d
  4. 07 Jul, 2015 1 commit
    • Thomas Miedema's avatar
      Build system: don't set GhcLibWays explicitly in build.mk.sample (#10536) · 37de4ad7
      Thomas Miedema authored
      We used to have the following in mk/build.mk.sample:
      
        GhcLibWays = $(if $(filter $(DYNAMIC_GHC_PROGRAMS),YES),v dyn,v)
      
      This commit removes that statement for the following reasons:
      
        1) It depends on the variable DYNAMIC_GHC_PROGRAMS, which is set later
           in the file for some BuildFlavours. Although this works because
           `make` does multiple passes when reading Makefiles, it is confusing
           to users [1]. Instead, test for DYNAMIC_GHC_PROGRAMS in
           mk/config.mk.in.
      
        2) Although it looks like that line is about compiling the `dyn` way,
           its purpose is really to not build the `prof` way. This commit
           introduces the variable BUILD_PROF_LIBS, to make this more
           explicit.
      
      This simplifies mk/build.mk.sample and mk/validate-settings.mk.
      
      Note that setting GhcLibWays explicitly still works, and
      DYNAMIC_GHC_PROGRAMS=NO in build.mk does not build the `dyn` way.
      
      [1] https://mail.haskell.org/pipermail/ghc-devs/2014-December/007725.html
      
      Differential Revision: https://phabricator.haskell.org/D1021
      37de4ad7
  5. 30 Jun, 2015 1 commit
  6. 02 Apr, 2015 2 commits
    • Thomas Miedema's avatar
      Disable same warnings for normal builds as for validate (#10223) · 4c1e1c87
      Thomas Miedema authored
      The default validate settings currently disable some warnings in the
      libraries. This patch moves those settings to a new file called
      `mk/warnings.mk`, and applies them also to normal builds.
      
      Through uncommenting a line in build.mk, developers can now build with
      -Werror.
      
      -Werror is not the default, because:
      * We can not guarantee that the build is warning free on platforms we
        don't run regularly run validate (as part of continuous integration
        systems), and we still want the build to go through on those
        platforms.
      * quoting rwbarton on irc > "I think -Werror by default has come up in
        the past and the argument was that it is too annoying when you are
        doing nontrivial development"
      
      Reviewed By: austin
      
      Differential Revision: https://phabricator.haskell.org/D785
      4c1e1c87
    • Thomas Miedema's avatar
      Do not set -fasm explicitly in build.mk.sample (#10223) · 9b66a7f3
      Thomas Miedema authored
      On platforms that support -fasm, it is already the default, so we don't
      have to set it.
      
      Reviewed By: austin, erikd (tested on powerpc and armhf)
      
      Differential Revision: https://phabricator.haskell.org/D784
      9b66a7f3
  7. 01 Apr, 2015 2 commits
  8. 31 Mar, 2015 1 commit
  9. 14 Dec, 2014 1 commit
  10. 09 Sep, 2014 1 commit
  11. 10 Aug, 2014 1 commit
  12. 29 Jun, 2014 1 commit
    • Herbert Valerio Riedel's avatar
      Add BUILD_DPH variable to GHC build-system · 88d85aa6
      Herbert Valerio Riedel authored
      
      
      Now that the `libraries/dph` submodule is checked out always we need
      a different way to disable building DPH to save compile-time while
      developing GHC.
      
      This commit adds a new YES/NO Make variable `BUILD_DPH` that can be used
      inside mk/build.mk to control whether to build libraries/dph or not.
      The default setting is `BUILD_DPH=YES` (via `mk/config.mk.in`).
      
      This also changes `validate`'s flag `--no-dph` to explicitly disable DPH
      for the current validation run.
      Signed-off-by: Herbert Valerio Riedel's avatarHerbert Valerio Riedel <hvr@gnu.org>
      
      Test Plan: successful validates with `--fast --no-dph`
      
      Differential Revision: https://phabricator.haskell.org/D31
      88d85aa6
  13. 10 Mar, 2014 2 commits
  14. 30 Jan, 2014 1 commit
  15. 28 Jan, 2014 1 commit
  16. 25 Oct, 2013 1 commit
  17. 02 Jul, 2013 1 commit
  18. 31 May, 2013 1 commit
  19. 04 May, 2013 1 commit
  20. 03 Apr, 2013 1 commit
  21. 15 Mar, 2013 1 commit
  22. 17 Jan, 2013 1 commit
  23. 25 Oct, 2012 1 commit
    • ian@well-typed.com's avatar
      Tweak build.mk.sample · 615268a1
      ian@well-typed.com authored
      Now that we can build dyn-only, we don't need to force
      DYNAMIC_BY_DEFAULT to NO. We just set GhcLibWays appropriately.
      615268a1
  24. 21 Oct, 2012 1 commit
  25. 18 Oct, 2012 1 commit
  26. 07 Aug, 2012 1 commit
  27. 13 Jan, 2012 1 commit
  28. 30 Aug, 2011 1 commit
  29. 08 Aug, 2011 1 commit
  30. 05 Aug, 2011 1 commit
  31. 20 Jul, 2011 1 commit
  32. 05 May, 2011 1 commit
  33. 04 May, 2011 1 commit
  34. 01 Feb, 2011 1 commit
  35. 16 Jun, 2010 1 commit
    • Ian Lynagh's avatar
      Rename some variables from FOO to FOO_CMD · 0481fe09
      Ian Lynagh authored
      This fixes a problem with commands like gzip, where if $GZIP is exported
      in the environment, then when make runs a command it'll put the Makefile
      variable's value in the environment. But gzip treats $GZIP as arguments
      for itself, so when we run gzip it thinks we're giving it "gzip" as an
      argument.
      0481fe09
  36. 09 Sep, 2009 1 commit
  37. 01 Jul, 2009 1 commit