1. 20 Sep, 2008 1 commit
  2. 19 Sep, 2008 4 commits
  3. 18 Sep, 2008 1 commit
  4. 12 Sep, 2008 1 commit
  5. 08 Sep, 2008 1 commit
  6. 07 Sep, 2008 1 commit
  7. 28 Aug, 2008 3 commits
  8. 24 Aug, 2008 3 commits
  9. 20 Aug, 2008 1 commit
  10. 17 Aug, 2008 2 commits
  11. 10 Aug, 2008 3 commits
  12. 29 Jul, 2008 1 commit
  13. 28 Jul, 2008 1 commit
  14. 20 Jul, 2008 1 commit
  15. 17 Jul, 2008 1 commit
  16. 16 Jul, 2008 1 commit
  17. 13 Jul, 2008 1 commit
  18. 08 Jul, 2008 1 commit
    • Ian Lynagh's avatar
      Get rid of compat/ · 2002bc3d
      Ian Lynagh authored
      Compat.Unicode is not utils/Unicode in the compiler.
      We build the hpc package with the stage1 compiler.
      Nothing else in the compat package was still used.
  19. 05 Jul, 2008 3 commits
  20. 03 Jul, 2008 2 commits
  21. 22 Jun, 2008 1 commit
  22. 08 Apr, 2008 1 commit
    • Simon Marlow's avatar
      Import libffi-3.0.4, and use it to provide FFI support in GHCi · e0fcf61d
      Simon Marlow authored
      This replaces the hand-rolled architecture-specific FFI support in
      GHCi with the standard libffi as used in GCJ, Python and other
      projects.  I've bundled the complete libffi-3.0.4 tarball in the
      source tree in the same way as we do for GMP, the difference being
      that we always build and install our own libffi regardless of whether
      there's one on the system (it's small, and we don't want
      dependency/versioning headaches).
      In particular this means that unregisterised builds will now have a
      fully working GHCi including FFI out of the box, provided libffi
      supports the platform.
      There is also code in the RTS to use libffi in place of
      rts/Adjustor.c, but it is currently not enabled if we already have
      support in Adjustor.c for the current platform.  We need to assess the
      performance impact before using libffi here too (in GHCi we don't care
      too much about performance).
  23. 16 Mar, 2008 1 commit
  24. 18 Feb, 2008 1 commit
    • chak@cse.unsw.edu.au.'s avatar
      All installed Haskell prgms have an inplace and an installed version · 3e274816
      chak@cse.unsw.edu.au. authored
      - GHC installs a range of compiled Haskell programs in addition to the actual
        compiler.  To ensure that they all run on the platform targeted by the build
        (which may have different libraries installed than the build host), we need
        to make sure that all compiled Haskell code going into an install is build
        with the stage 1 compiler, not the bootstrap compiler.  Getting this right
        is especially important on the Mac to enable builds that work on Mac OS X
        versions that are older than the one performing the build.
      - For all installed utils implemented in Haskell (i.e., ghc-pkg, hasktags,
        hsc2hs, runghc, hpc, and pwd) we compile two versions, an inplace version
        and a version for installation.  The former is build by the bootstrap
        compiler during the stage 1 build and the latter is build by the stage 1
        compiler during the stage 2 build.
      - This is really very much as the setup for ghc itself, only that we don't use
        separate stage1/ and stage2/ build directories.  Instead, we clean before
        each build.  CAVEAT: This only works properly if invoked from the 
        toplevel Makefile.
      - Instead of UseStage1=YES (as used by the previous binary-dist-specific
        recompilation), we now use the same $(stage) variables as used for the
        compiler proper - to increase uniformity and to avoid extra conditionals for
        the install target.
  25. 05 Feb, 2008 1 commit
  26. 02 Feb, 2008 1 commit
    • chak@cse.unsw.edu.au.'s avatar
      First stab at an installer package for the Mac · c222ce6d
      chak@cse.unsw.edu.au. authored
      - GHC as a Mac framework
      - I tried to make a package where the user could choose whether to install
        in /Library/Frameworks or ~/Library/Frameworks (to allow installation for
        non-admins).  However, that doesn't work well without including the whole
        distribution twice as the decision as to whether the admin password needs
        to be entered is made at packaging time (not at install time).
  27. 18 Dec, 2007 1 commit