Hi guys,
Just wanted to report on the steps/hacks to a successful build of GHC HEAD
on OS X 10.9 thanks to help from Carter Schonwald and Austin Seipp.
1) I installed LLVM 3.4
brew install llvm --with-clang --HEAD
2) I used this build.mk:
HADDOCK_DOCS = NO
BUILD_DOCBOOK_HTML = NO
On Fri, 9 Aug 2013, Luke Iannini wrote:
Hi guys,
Just wanted to report on the steps/hacks to a successful build of GHC HEAD on
OS X
10.9 thanks to help from Carter Schonwald and Austin Seipp.
HEAD as of 3e598fe0b? I wasn't able to build that one because the Core
lint pass fails with the new
Yes, I'm at 3e598fe0b, couldn't tell you why it worked for me though : ).
On Fri, Aug 9, 2013 at 3:33 AM, Dr. ERDI Gergo ge...@erdi.hu wrote:
On Fri, 9 Aug 2013, Luke Iannini wrote:
Hi guys,
Just wanted to report on the steps/hacks to a successful build of GHC
HEAD on OS X
10.9 thanks to
OK -- the page is up at http://ghc.haskell.org/trac/ghc/wiki/Newcomers
Please improve it as you see fit!
Richard
On 2013-08-06 07:04, Vincent Hanquez wrote:
On 08/05/2013 10:51 AM, Richard Eisenberg wrote:
I think a hacking session is a great idea, either over IRC or at ICFP.
I'm also
Hi,
I'm brand new to GHC development, and have been looking at:
http://ghc.haskell.org/trac/ghc/ticket/4243
I was initially thinking of something like getopt_long_only, as per:
http://linux.die.net/man/3/getopt_long
however it looks like the portability of that function isn't the greatest,
I've had to deal with the stage 1 compiler for two different reasons:
- I check out a new tree to work on a new task, and I forget to build
before modifying the code.
- I'm working on a tree with a working stage-1 compiler, but then I
change the interface file format. After the stage-2
Hi all,
I just started GHC development made a commit for ticket 7401:
http://ghc.haskell.org/trac/ghc/ticket/7401
My patch is here:
https://github.com/osa1/ghc/commit/3ec257ff48372de30df59cd8854ce28954c9db95
`make test` succeeds. My test case for this patch is something like this:
data D
Hello Omer,
It is almost certainly the case that the implementation of these
functions should not be the constant return True function. Furthermore,
the implementation should probably be done using:
http://ghc.haskell.org/trac/ghc/ticket/2431
Edward
Excerpts from Ömer Sinan Ağacan's
Hello all,
Herbert and I have decided to do the Gitolite migration today, since
it's a slow Friday and there should be small impact overall.
We will be performing the switch at 8:30pm UTC/GMT, which is almost
exactly three hours from now. We expect it will take less than thirty
minutes.
For all
All,
Push access is now restored and Gitolite is in place! This brings some
nice updates:
* There's now access to the 'git' protocol for cloning anonymously.
This lets you clone even the biggest repos extremely quickly, and is
the fastest method for getting a copy of the tree.
* Firewalled?
Hello all,
How would people feel about an alternate GC implementation in GHC which
is not parallel? A GC like this would be simpler to understand, maybe a
little faster when parallel collection is not being used, and (most
importantly for my case) easier to extend with interesting features.
In
Hi David,
I was initially thinking of something like getopt_long_only, as per:
http://linux.die.net/man/3/getopt_long
however it looks like the portability of that function isn't the greatest,
and from looking at rts/RtsFlags.c:procRtsOpts(...) it might not be the
best solution.
That's
Hi Edward,
I was more worried about the effect that it would have on the 2nd tier
platforms, some of which don't have getopt_long_only - which I think is
desirable due to the two-character short options that need to be dealt
with.
My feeling is that writing and maintaining a correct
13 matches
Mail list logo
