On 30/03/2011 13:52, Ian Lynagh wrote:
On Wed, Mar 30, 2011 at 09:40:06AM +0100, Simon Marlow wrote:
On 29/03/2011 14:55, Ian Lynagh wrote:
I think it would make a lot of sense for GHC to know the paths to the
tools that it was built with, even when it doesn't actually use them
itself. That wa
On Wed, Mar 30, 2011 at 09:40:06AM +0100, Simon Marlow wrote:
> On 29/03/2011 14:55, Ian Lynagh wrote:
> >
> >I think it would make a lot of sense for GHC to know the paths to the
> >tools that it was built with, even when it doesn't actually use them
> >itself. That way, "ghc --info" can say e.g.
On 29/03/2011 14:55, Ian Lynagh wrote:
On Tue, Mar 29, 2011 at 10:10:56AM +0100, Simon Marlow wrote:
On 29/03/2011 00:15, Mark Lentczner wrote:
== Autoconf ==
Autoconf offers only limited support for cross compiling. While it
professes to know about three platforms, base, host, and target; it
On Tue, Mar 29, 2011 at 10:10:56AM +0100, Simon Marlow wrote:
>
> On 29/03/2011 00:15, Mark Lentczner wrote:
> >
> >== Autoconf ==
> >Autoconf offers only limited support for cross compiling. While it
> >professes to know about three platforms, base, host, and target; it
> >knows only about one to
Hi Mark,
On 29/03/2011 00:15, Mark Lentczner wrote:
As you may know, I'm trying to patch the GHC build to support building
cross-compilers:
== General Problem ==
The most general case is a user on build platform B, wishing to build a
GHC that runs on host platform H which produces code that run
As you may know, I'm trying to patch the GHC build to support building
cross-compilers:
== General Problem ==
The most general case is a user on build platform B, wishing to build a GHC
that runs on host platform H which produces code that runs on target
platform T. But, we need not handle such a
