- Aug 28, 2013
-
-
Austin Seipp authored
iOS has some particular constraints about how applications can be built: * We must generate a static library (.a) since XCode does the final link. * We need to carefully give the right set of arguments to libtool in the case we're generating an archive. * Dynamic linking isn't supported. * It can only be done on OS X. This patch cleans up all of the above. We add a new flag `-staticlib` (only supported on Darwin) that allows us to produce archive files using libtool, and a -pgmlibtool flag to control which 'libtool' executable to use. This fixes #8127. I believe this is the last piece missing from the iOS cross compiler. Authored-by: Luke Iannini <lukexi@me.com> Authored-by: Maxwell Swadling <maxwellswadling@gmail.com> Authored-by: Stephen Blackheath <...@blacksapphire.com> Signed-off-by: Austin Seipp <aseipp@pobox.com>
-
- Mar 18, 2013
-
-
Ian Lynagh authored
Without it, when linking the split objects for Language.Haskell.TH.Syntax, the commandline was too long when listing all the files directly.
-
- Feb 25, 2013
-
-
Gabor Greif authored
This fixes certain older GCCs which do not accept link options when assembling or compiling: ppc_85xx-gcc: --hash-size=31: linker input file unused because linking not done ppc_85xx-gcc: --reduce-memory-overheads: linker input file unused because linking not done and diagnose this to stderr.
-
- Jan 17, 2013
-
-
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=<..>
-
- Aug 07, 2012
-
-
Ian Lynagh authored
To explicitly choose whether you want an unregisterised build you now need to use the "--enable-unregisterised"/"--disable-unregisterised" configure flags.
-
- Aug 05, 2012
-
-
Ian Lynagh authored
Related to #4862
-
Ian Lynagh authored
They were getting baked into Config.hs before.
-
- Jan 14, 2012
-
-
Ian Lynagh authored
We want to use the inplace ar, rather than whichever ar the machine that we build on happens to have.
-
- Jan 10, 2012
-
-
David Terei authored
Patch from Karel Gardas!
-
- Jan 04, 2012
-
-
Simon Marlow authored
Now target32bit works for all targets without any manual intervention, as it should do. #5735 was a portability regression.
-
- Dec 08, 2011
-
-
PHO authored
.ident directives are usually ignored by as(1), and in some cases (like Darwin/PPC) they even raise an error.
-
- Oct 19, 2011
-
-
Ian Lynagh authored
-
Ian Lynagh authored
-
Ian Lynagh authored
-
- Jun 22, 2011
-
-
Ian Lynagh authored
-
Ian Lynagh authored
This is a little cleaner, and removes a barrier to cross-compiling to/from Windows. There are a few more tools that still need to be handled in the same way.
-
- Apr 29, 2011
-
-
Ian Lynagh authored
-
Ian Lynagh authored
I've made cpp_args include gcc_args. It effectively didn't before, but seeing as gcc_args sometimes has -D flags in, I think doing so is the right thing to do.
-
- Apr 23, 2011
-
-
Ian Lynagh authored
-
Ian Lynagh authored
Makes it consistent with the existing "C compiler flags" field.
-
- Apr 22, 2011
-
-
Ian Lynagh authored
They were hardcoded in Config.hs
-
- Apr 21, 2011
-
-
Ian Lynagh authored
-