Dear devs,
I'm getting this build error when compiling GHC:
inplace/bin/ghc-stage1 -hisuf hi -osuf o -hcsuf hc -static -H64m -O0
-fasm-package-name ghc-prim-0.3.1.0 -hide-all-packages -i
-ilibraries/ghc-prim/. -ilibraries/ghc-prim/dist-install/build
The problem with these kind of commit-time checks is that you only find
out the problem *after* you've validated your nicely polished commits.
This is easily solved by adding this line to .emacs file:
(add-hook 'before-save-hook 'delete-trailing-whitespace)
No more trailing whitespaces.
Hello Herbert,
I think that current GHC HEAD's primitive and vector are undesirable version.
Because:
1. GHC HEAD's primitive and vector are older than latest released version.
(You already pointed out that.）
2. But ... GHC HEAD's primitive and vector have some changes from older
The problem with this approach is that if a file already contains
trailing whitespace, you'll introduce spurious changes in your commit.
I wouldn't call it a problem, but a feature - provided that you put whitespace
changes in a separate commit. In this way we would gradually get rid of all
Different package authors have different policies, but if the use of a few
#ifdefs allows compatibility with more ghc versions, I think most folks
would consider that a win.
On Thursday, August 29, 2013, Jan Stolarek wrote:
I'm still not sure how to handle libraries that I modified with my
Hi,
Cabal 1.18 is still in the release candidate stage so it has in fact not
been released yet. We could either bump the dependency on base to 4.8
before the 1.8 release or we could make a Cabal-1.8.0.1 release together
with the GHC release that bumps the dependency.
-- Johan
On Wed, Aug 28,
On 2013-08-29 12:20, Dan Rosén wrote:
I'm getting this build error when compiling GHC
Just as a remark, I'm getting the same error, presumably because Dan and
me were working on the same modules. To put the error in perspective,
here's how I got it: After editing a few lines in PrelNames.lhs and
Other than using integer-simple I haven't done anything strange, just
standard mingw. I'm using the 'quick' flavour in my build.mk.
One thing to try is to use -d with make (and maybe tee the output to a
file, it produces tons of stuff). Then it may be possible to pinpoint where
it hangs.
Niklas
When was the last time you cleaned your tree? Earlier this week I made a
breaking change to the interface file format. If you have a build from
before then, update and incrementally rebuild, it will break.
On Thursday, August 29, 2013, David Luposchainsky wrote:
On 2013-08-29 12:20, Dan Rosén
Links like this one fail to work. Is this permanent? Thanks!
http://www.haskell.org/pipermail/cvs-ghc/2007-July/036496.html
Microsoft Research Limited (company number 03369488) is registered in England
and Wales
Registered office is at 21 Station Road, Cambridge, CB1 2FB
FYI I just pushed a commit (cf http://ghc.haskell.org/trac/ghc/wiki/LateDmd)
that changes the format of the .hi files — so it's safest to do a full
rebuild once you pull it.
___
ghc-devs mailing list
ghc-devs@haskell.org
I've collected the main points of this discussion on the wiki.
http://ghc.haskell.org/trac/ghc/wiki/Commentary/Compiler/Backends/LLVM/ReplacingNCG
Ben.
On 28/08/2013, at 2:51 AM, Austin Seipp wrote:
Well, what's the long term plan? Is the LLVM backend going to
become the only backend at
12 matches
Mail list logo
