| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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=<..>
|
|
|
|
|
| |
Anything that uses gcc needs to happen after we've made the mingw
inplace tree on Windows.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
All supported bootstrapping compilers now have --info output,
so we can use that unconditionally.
|
|
|
|
| |
We no longer actually use ITIMER_VIRTUAL anyway
|
|
|
|
|
|
| |
To explicitly choose whether you want an unregisterised build you now
need to use the "--enable-unregisterised"/"--disable-unregisterised"
configure flags.
|
|
|
|
| |
Related to #4862
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The test isn't very pretty; it involves trawling through the
objdump -p output. I couldn't find an easier way, unfortuantely.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
This patch enhances Platform's ArchARM to include ARM ABI value. It also
tweaks configure machinery to detect hard-float ABI and to set it wherever
needed. Finally when hard-float ABI is in use, pass appropriate compiler
option to the LLVM's llc. Fixes #5914.
|
|
|
|
| |
Xcode 4.3 installs the command line tools in a different location as earlier versions of Xcode. With the bootstrapping info, the build fails if the bootstrap compiler was built with an older version of Xcode.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
The Win64 mingw zip file isn't in the ghc-tarballs repo, as it's >300M.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Patchset from Stephen Blackheath <stephen.blackheath@ipwnstudios.com>
|
|
|
|
|
| |
We want to use the inplace ar, rather than whichever ar the
machine that we build on happens to have.
|
|
|
|
| |
Patch from Karel Gardas!
|
| |
|
|
|
|
|
| |
Now target32bit works for all targets without any manual intervention,
as it should do. #5735 was a portability regression.
|
| |
|
| |
|
|
|
|
|
| |
Some platforms use linkers that don't support the --hash-size=31 and
--reduce-memory-overheads flags.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch adds support to the autoconf scripts to detect
when we are using a C compiler that uses an LLVM back end.
An LLVM back end does not support all of the extensions use
by GCC, so we need to perform some conditional compilation
in the runtime, particularly for handling thread local
storage and global register variables.
The changes here will set the CC_LLVM_BACKEND in the
autoconf scripts if we detect an llvm-based compiler. We use
this variable to define the llvm_CC_FLAVOR variable that we
can use in the runtime code to conditionally compile for
LLVM.
|
| |
| |
| |
| | |
We now make use of the ghc-packages file when making the haddock index.
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
$TargetOS_CPP wasn't getting defined in a bindist, which meant the
code to use gcc-4.2 instead of gcc on OS X wasn't working. Now fixed,
by moving some of configure.ac's code into the shared aclocal.m4.
|
|
|
|
|
| |
However, one perf test fails (parsing001) due to extra allocation. I
want to look into this so I'm not bumping it just yet.
|
| |
|
|
|
|
|
|
| |
yet, and fixing it is non-trivial (a change to Cabal is needed). So
I'm making configure fail with an error suggesting to install an older
Alex for now.
|
| |
|