1. 02 Nov, 2017 1 commit
  2. 27 Sep, 2017 1 commit
  3. 28 Jul, 2017 1 commit
    • Moritz Angermann's avatar
      Add “BINARY_DIST_DIR” to Makefile · 274e9b27
      Moritz Angermann authored
      This allows to customize the location where binary distributions are
      placed with `make binary-dist`.
      
      E.g. using:
      ```
      BINARY_DIST_DIR=/path/to/bindists make binary-dist
      ```
      will place binary dists outside of the source tree into the given
      folder.
      
      This change falls back to ".", which is the old behaviour.
      
      Test Plan: build binary-dist
      
      Reviewers: bgamari, austin
      
      Reviewed By: bgamari
      
      Subscribers: rwbarton, thomie
      
      Differential Revision: https://phabricator.haskell.org/D3798
      274e9b27
  4. 06 Aug, 2016 1 commit
  5. 09 Feb, 2016 1 commit
  6. 12 Dec, 2015 1 commit
  7. 20 Sep, 2015 1 commit
    • Edward Z. Yang's avatar
      Always run explicitly requested ways (extra_ways) for fast runs. · b89c4913
      Edward Z. Yang authored
      To keep validates fast, we only one run one way.  But I think that
      it's important for some tests to run them a few ways, just to
      make sure functionality, e.g. the profiler, is working.  This commit
      changes the logic so that any way specified in extra_ways is always
      run for fast.  The big changes is now profiling tests are run on
      validate.
      
      I also made it so the G1 garbage collector tests only run on slow.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      
      Test Plan: validate
      
      Reviewers: austin, thomie, bgamari
      
      Reviewed By: austin, thomie, bgamari
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D1251
      b89c4913
  8. 07 Sep, 2015 1 commit
  9. 04 Sep, 2015 1 commit
  10. 02 Sep, 2015 1 commit
    • thomie's avatar
      Testsuite: by default run all tests for a single way · c43c8e2c
      thomie authored
      `make test` now runs all tests for a single way only. Use `make slowtest` to
      get the previous behaviour (i.e. run all tests for all ways).
      
      The intention is to use this new `make test` setting for Phabricator, as
      a reasonable compromise between `make fasttest` (what it previously
      used) and a fullblown `make slowtest` (which runs all tests for all
      ways).
      
      See Note [validate and testsuite speed] in toplevel Makefile.
      
      Differential Revision: https://phabricator.haskell.org/D1178
      c43c8e2c
  11. 13 Jul, 2015 1 commit
  12. 02 Jul, 2015 1 commit
  13. 04 Jun, 2015 2 commits
    • thomie's avatar
      Make validate more quiet · d0063e89
      thomie authored
        * By default use V=0, and call the testsuite with VERBOSE=2, which we
          did before only with validate --quiet. This disables printing the
          test commands it runs.
      
        * When --quiet is used, call the testsuite with VERBOSE=1. This
          disables printing the '====> Scanning' lines, and doesn't print
          which test is being run. So it only prints something when a test
          accidentally prints to stdout or when it fails.
      
          Don't set this option on Travis, as Travis will cancel a build if it
          doesn't see any output for more than 10 minutes.
      
        * When --quiet is used, set the new test option NO_PRINT_SUMMARY,
          which skips printing the test summary. Only the list of unexpected
          failures is printed, if there are any. Note that the full summary
          can still be found in testsuite_summary.txt
      
        * When --quiet is used, don't pass the `-v` flag to `ghc-pkg check`
      
        * When --quiet is used, don't print the Oops! header. It shoud be
          clear from the list of failing tests that something is wrong.
      
      This is all done to get the most out of 30 lines of logfile. These changes can
      be disabled later by simply not passing the --quiet flag to validate.
      
      Differential Revision: https://phabricator.haskell.org/D942
      d0063e89
    • thomie's avatar
      Build: ./boot && ./configure && make sdist (#8723) · 092082e7
      thomie authored
      Make it possible to run `make sdist` right after configure, without completing
      a complete build first.
      
      Test Plan:
      I compared the contents of the created `.tar.bz2` files in the `sdistprep`
      directory, after running `make sdist` both before and after completing a full
      build, using `diff -r`. There weren't any differences (after applying the
      patches from D914).
      
      Note that the `.tar.bz2` files were not exactly the same size, but they aren't
      either when tarring and bzipping the same directory twice. It seems tarring
      and bzipping is not deterministic (on my system).
      
      Differential Revision: https://phabricator.haskell.org/D917
      092082e7
  14. 30 May, 2015 4 commits
  15. 07 Mar, 2015 1 commit
  16. 02 Mar, 2015 1 commit
    • thomie's avatar
      `make test` in root directory now runs fulltest · 31d4f2e9
      thomie authored
      Summary:
      Currently, running `make test` in:
        /                   runs fast testsuite
        /testsuite          doesn't work
        /testsuite/tests    runs slow testsuite
      
      This commit:
        * changes `make test` in the ghc root directory to run the slow testsuite,
          just like it already does in `testsuite/tests`
        * adds some simple targets to `/testsuite`, that all delegate to
          `/testsuite/tests`
        * adds a new target `fasttest` to the toplevel Makefile, with a shorthand
          name `fast` (for consistency with /testsuite and /testsuite/tests)
        * declares some more targets PHONY for safety
      
      Wiki pages that need updating:
        * Building/StandardTargets
        * Buliding/RunningTests
      
      Reviewers: austin
      
      Reviewed By: austin
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D685
      31d4f2e9
  17. 19 Aug, 2014 1 commit
  18. 27 Apr, 2014 1 commit
  19. 22 Apr, 2014 1 commit
  20. 28 Feb, 2014 1 commit
  21. 14 Jan, 2014 1 commit
  22. 01 Oct, 2013 1 commit
  23. 25 May, 2013 1 commit
  24. 18 May, 2013 1 commit
  25. 20 Jul, 2011 2 commits
  26. 05 May, 2011 1 commit
  27. 07 Feb, 2011 1 commit
  28. 27 Jan, 2011 1 commit
  29. 22 Jan, 2011 1 commit
    • Ian Lynagh's avatar
      Simplify the build system, and remove 2 phases · 295016c3
      Ian Lynagh authored
      From
          http://hackage.haskell.org/trac/ghc/wiki/Building/Architecture/Idiom/PhaseOrdering
      
      Phase 0:
          Includes: package-data.mk files for things built by the
                    bootstrapping compiler.
          Builds:   the dependency files for hsc2hs and genprimopcode. We need
                    to do this now, as hsc2hs needs to be buildable in phase 1's
                    includes (so that we can make the hpc library's .hs source
                    files, which in turn is necessary for making its dependency
                    files), and genprimopcode needs to be buildable in phase 1's
                    includes (so that we can make the primop-*.hs-incl files,
                    which are sources for the stage1 compiler library, and thus
                    necessary for making its dependency files).
      Phase 1:
          Includes: dependency files for things built by the bootstrapping
                    compiler.
          Builds:   package-data.mk files for everything else. Note that this
                    requires configuring the packages, which means telling cabal
                    which ghc to use, and thus the stage1 compiler gets built
                    during this phase. 
      Phase "":
          Includes: dependency files for everything else.
          Builds:   Everything else. 
      295016c3
  30. 16 Jan, 2011 1 commit
  31. 15 Jan, 2011 1 commit
    • Ian Lynagh's avatar
      Build system improvements · a3be88fd
      Ian Lynagh authored
      We no longer use dummy-ghc; instead we don't configure most packages
      until the stage1 compiler is available.
        
      We also now use Cabal for building the ghc-bin package.
      
      There are a couple more sanity checks too.
      a3be88fd
  32. 30 Sep, 2010 1 commit
  33. 29 Jul, 2010 2 commits
  34. 16 Nov, 2009 1 commit