Conal Elliott wrote:
Thanks for that tip.
Here's what the problematic file contains:
1 24 MOVEABLE PURE "dist\build\eros\eros.exe.manifest"
Now I can see that the "unrecognized escape sequences" come from missing
back-slashes. I guess "dist\build", the "\b" is getting interpreted as
a back
Conal Elliott wrote:
Thanks for that tip.
Here's what the problematic file contains:
1 24 MOVEABLE PURE "dist\build\eros\eros.exe.manifest"
Now I can see that the "unrecognized escape sequences" come from missing
back-slashes. I guess "dist\build", the "\b" is getting interpreted as
a back
Thanks for that tip.
Here's what the problematic file contains:
1 24 MOVEABLE PURE "dist\build\eros\eros.exe.manifest"
Now I can see that the "unrecognized escape sequences" come from missing
back-slashes. I guess "dist\build", the "\b" is getting interpreted as a
backspace, thus becoming "dis
On Fri, Sep 07, 2007 at 08:47:43AM -0700, Conal Elliott wrote:
>
> I don't know what was in c:/tmp/ghc2268_0/ghc2268_0.rc. It was gone before
> I could look.
If you add the -keep-tmp-files flag then it shouldn't be deleted.
Thanks
Ian
___
Cvs-ghc ma
I get this very same error on a clean build with STABLE ghc-6.8.20070909 (on
Windows). Any ideas on what's going wrong here and how to fix it?
- Conal
On 9/7/07, Conal Elliott <[EMAIL PROTECTED]> wrote:
>
> I get the following error while linking haddock.ghc using the snapshot
> ghc-6.7.200708
I get the following error while linking haddock.ghc using the snapshot
ghc-6.7.20070824-i386-unknown-mingw32.exe .
...
[17 of 17] Compiling Main ( src/Main.hs,
dist\build\haddock\haddock-tmp/Main.o )
Linking dist\build\haddock\haddock.exe ...
c:/tmp/ghc2268_0/ghc2268_0.r
