Skip to content
Snippets Groups Projects
  1. Apr 16, 2016
    • Herbert Valerio Riedel's avatar
      Rework CC/CC_STAGE0 handling in `configure.ac` · 865602e0
      Herbert Valerio Riedel authored and Ben Gamari's avatar Ben Gamari committed
      Rather than using the non-standard/idiomatic `--with-{gcc,clang}=...`
      scheme use the `CC=...` style scheme.
      
      The basic idea is to have Autoconf's CC/CFLAG/CPPFLAG apply to
      stage{1,2,3}, while having a separate _STAGE0 set of env-vars
      denote the bootstrap-toolchain flags/programs.
      
      This should be simpler, less confusing, and somewhat more in line with
      Autoconf's idioms (allowing us to reuse more of Autoconf rather than
      (re)inventing our own confusing non-standard m4 macros to do stuff that
      Autoconf could almost do already for us)
      
      Morever, expose CC_STAGE0 as a so-called "precious" variable.
      
      So now we can better control which bootstrapping gcc is used
      (by default the one used by the stage0 ghc, unless CC_STAGE0 is
      overriden)
      
      ```
      Some influential environment variables:
        CC_STAGE0   C compiler command (bootstrap)
        CC          C compiler command
        CFLAGS      C compiler flags
        ...
      
      Use these variables to override the choices made by `configure' or to
      help it to find libraries and programs with nonstandard names/locations.
      ```
      
      Test Plan: I've tested that cross-compiling with
      `--target=powerpc-linux-gnu` still works, and tried a few variants of
      settting `CC=` and `CC_STAGE0=`; `./validate` passed as well
      
      Reviewers: erikd, austin, bgamari, simonmar
      
      Reviewed By: simonmar
      
      Subscribers: Phyx, thomie
      
      Differential Revision: https://phabricator.haskell.org/D2078
      865602e0
  2. Oct 30, 2015
  3. Feb 26, 2014
  4. Oct 01, 2013
  5. Mar 01, 2013
  6. May 15, 2012
    • pcapriotti's avatar
      Rename package-conf flags to package-db. · ca2debb2
      pcapriotti authored
      Rename package database flags in both GHC and ghc-pkg so that they are
      consistent with Cabal nomenclature.
      
      Add a version check to the build system so that the correct set of
      package db flags are used when the bootstrapping GHC has version < 7.5.
      ca2debb2
  7. Mar 31, 2011
  8. Dec 16, 2010
  9. Dec 10, 2010
  10. Nov 20, 2010
  11. Sep 21, 2010
  12. Jun 16, 2010
  13. May 08, 2010
  14. Apr 15, 2010
  15. Nov 30, 2009
  16. Nov 25, 2009
  17. Sep 27, 2009
  18. Jun 13, 2009
  19. May 14, 2009
  20. May 04, 2009
  21. Apr 28, 2009
  22. Apr 26, 2009
  23. Feb 10, 2009
    • Ian Lynagh's avatar
      Don't use the absolute path to the bindist tarball · f75d258c
      Ian Lynagh authored
      On Windows, we end up doing something like
          rsync c:/build/ghc-6.10.1-unknown-mingw32.tar.bz2 haskell.org:dist
      and it thinks that it is meant to get the file from the host called "c".
      Now we just do
          rsync ghc-6.10.1-unknown-mingw32.tar.bz2 haskell.org:dist
      so rsync understand what we mean.
      f75d258c
  24. Sep 12, 2008
  25. Aug 24, 2008
  26. Dec 07, 2007
  27. Nov 15, 2007
  28. Sep 05, 2007
  29. Aug 23, 2007
  30. Aug 22, 2007
Loading