1. 13 Mar, 2013 1 commit
  2. 11 Mar, 2013 1 commit
  3. 03 Mar, 2013 6 commits
  4. 02 Mar, 2013 4 commits
  5. 01 Mar, 2013 5 commits
  6. 26 Feb, 2013 1 commit
  7. 21 Feb, 2013 4 commits
  8. 20 Feb, 2013 1 commit
  9. 17 Feb, 2013 2 commits
  10. 16 Feb, 2013 2 commits
  11. 15 Feb, 2013 1 commit
  12. 05 Feb, 2013 1 commit
    • ian@well-typed.com's avatar
      Add a dependency of program modules on GHC.TopHandler · 40e43fa2
      ian@well-typed.com authored
      If you were unlucky, the build could fail, e.g.:
      
      utils\mkUserGuidePart\Main.hs:1:1:
          Failed to load interface for `GHC.TopHandler'
          There are files missing in the `base' package,
          try running 'ghc-pkg check'.
          Use -v to see a list of the files searched for.
      utils/mkUserGuidePart/ghc.mk:18: recipe for target `utils/mkUserGuidePart/dist/build/Main.o' failed
      40e43fa2
  13. 29 Jan, 2013 2 commits
  14. 25 Jan, 2013 1 commit
  15. 24 Jan, 2013 1 commit
  16. 17 Jan, 2013 1 commit
    • Simon Marlow's avatar
      Tidy up cross-compiling · 109a1e53
      Simon Marlow authored
      We have two cases:
       1. building a cross-compiler
       2. compiling GHC to run on a foreign platform
      
      These two are done with almost the same setup: (1) is the stage 1
      compiler, and (2) is the stage 2 compiler, when CrossCompiling=YES.
      
      The only difference between (1) and (2) is that you if you set up the
      build for (1), then it stops before stage 2 and you can 'make install'
      to install stage 1.
      
      Unfortunately, (2) didn't work, and the build system code needed some
      tidying up.
      
      Change to the way the build is set up:
      
      Before
      ------
      
      To build a cross-compiler:
        ./configure --target=<..>
      
      To compile a foreign GHC:
        ./configure --host=<..> --target=<..>
      
      Now
      ---
      
      To build a cross-compiler:
        ./configure --target=<..>
        And set "Stage1Only=YES" in mk/build.mk
      
      To compile a foreign GHC:
        ./configure --target=<..>
      109a1e53
  17. 10 Jan, 2013 1 commit
  18. 02 Jan, 2013 1 commit
  19. 30 Nov, 2012 1 commit
  20. 29 Nov, 2012 1 commit
    • ian@well-typed.com's avatar
      Add configure option to use system provided libffi; fixes #5743 · 3005e909
      ian@well-typed.com authored
      Based on patch from Peter Trommler:
      
          From 293495d40f62e691520331a41c6d85d82e120169 Mon Sep 17 00:00:00 2001
          From: Peter Trommler <ptrommler@acm.org>
          Date: Sun, 21 Oct 2012 18:47:01 +0200
          Subject: [PATCH] Add configure option to use system provided libffi This
           fixes track # 5743 and #4496.
      3005e909
  21. 13 Nov, 2012 1 commit
  22. 12 Nov, 2012 1 commit
    • ian@well-typed.com's avatar
      Replace mkDerivedConstants.c with DeriveConstants.hs · f49271c0
      ian@well-typed.com authored
      DeriveConstants.hs works in a cross-compilation-friendly way. Rather
      than running a C program that prints out the constants, we just compile
      a C file which has the constants are encoded in symbol sizes. We then
      parse the output of 'nm' to find out what the constants are.
      
      Based on work by Gabor Greif <ggreif@gmail.com>.
      f49271c0