On Tue, Sep 16, 2008 at 02:43:42PM +0100, Mitchell, Neil wrote:
>
> The problem is that perl on my PATH is the ghc-6.8.3 one
I don't think that that is supposed to to work, and I'm a bit confused
why it is the first perl in your path because I thought that you said
that you added that directory t
Hi Simon,
> I object (mildly) to having multiple sets of build
> instructions.
I object strongly, which is why Claus's instructions with an exact set
of instructions with absolutely no choices provided is so great. By
"preparing a set of instructions", I really just mean updating the
existing in
Mitchell, Neil wrote:
Hi
My preference is to use the latest versions, otherwise we'll
run into
some other bug and the mingw people will (legitimately) tell
us to use
a newer version, requiring us to upgrade everything anyway. I think
Claus disagrees with me on this.
Actually, I don't disagr
Hi
> >My preference is to use the latest versions, otherwise we'll
> run into
> >some other bug and the mingw people will (legitimately) tell
> us to use
> >a newer version, requiring us to upgrade everything anyway. I think
> >Claus disagrees with me on this.
>
> Actually, I don't disagree.
Hi
> > 2) cc1 is in the wrong place, and can't be found.
>
> isn't this just the fact that Cabal needs to pass -B to gcc?
> Does anyone know why we're still haven't this problem?
No idea. If you think its now fixed, let me know and I'll try again
without the modifications to my PATH.
> > 3) o
Mitchell, Neil wrote:
| Yes, I've added notes where my experiences differ. Once I've got
| everything working, and have identified which steps are going to be
| worked around by the build system (i.e. cc1 issues), I'll merge my
| changes in.
Thank you! Do let me know when you do this.
Befo
Before I fix the documentation the GHC team needs to make a decision -
do you want to support the latest mingw/cygwin, or advise people to use
specific old versions?
The old versions work exactly as per the descriptions Claus gave
(although there are a few tweaks required for bootstrapping with
> | Yes, I've added notes where my experiences differ. Once I've got
> | everything working, and have identified which steps are going to be
> | worked around by the build system (i.e. cc1 issues), I'll merge my
> | changes in.
>
> Thank you! Do let me know when you do this.
Before I fix the
| Yes, I've added notes where my experiences differ. Once I've got
| everything working, and have identified which steps are going to be
| worked around by the build system (i.e. cc1 issues), I'll merge my
| changes in.
Thank you! Do let me know when you do this.
Simon
_
Hi Simon
> I'd really really like to end up
> a) with a build system that works
> b) with Wiki instructions that match it
The issues with (a) are fairly minor, so I don't think that will be too
much effort.
> Concerning the latter, Neil, you could fix the Wiki material
> directly couldn't you?
x the Wiki material directly couldn't
you? That would be great.
Simon
| -Original Message-
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
| Behalf Of Mitchell, Neil
| Sent: 16 September 2008 14:44
| To: cvs-ghc@haskell.org
| Subject: RE: Windows build issues
|
| Hi
|
| I c
Hi
I can fix the error with the patch:
hunk ./docs/man/Makefile 26
- perl gen_flags.xsl.pl "$(GHC_COMMANDS)" "$(libdir)" > $@
+ ./gen_flags.xsl.pl "$(GHC_COMMANDS)" "$(libdir)" > $@
The problem is that perl on my PATH is the ghc-6.8.3 one, which doesn't
work. The shebang line is /usr
12 matches
Mail list logo
