Hi devs
I've got my Linux box upgraded to a recent version of Ubuntu, so I'm no longer
stuck on gcc version.
But I can't build either. Something strange with /lib/cpp fails sanity check.
The log is below.
Can anyone help? I'm a bit stalled.
This call to "make" follows the same failure when I ty
Digging around online, I suspect that you may not have the GNU C++ compiler
installed at all. Take this with a shaker of salt.
David FeuerWell-Typed, LLP
Original message From: Simon Peyton Jones via ghc-devs
Date: 11/20/17 8:14 AM (GMT-05:00) To:
ghc-devs@haskell.org Subje
Is anyone else getting an absolute flood of commit emails related to
haddock? I remember this happening a little while back with the hadrian
merge into the GHC tree.
Best,
_ara
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bi
Ara Adkins writes:
> Is anyone else getting an absolute flood of commit emails related to
> haddock? I remember this happening a little while back with the hadrian
> merge into the GHC tree.
>
Indeed it seems that the commit hook is running amuck [1]
Herbert, do you know what we can do about th
I’m getting them too ☹
From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Ara Adkins
Sent: 20 November 2017 21:07
To: GHC developers
Subject: Commit Notifications Flood
Is anyone else getting an absolute flood of commit emails related to haddock? I
remember this happening a littl
I've put a redirect rule on them for now, but given that this is the second
time that it's happened (as far as I know), is it possible to modify the
way in which the commit hook sends notifications for new branches with a
significant history? I don't really know much about the exact message
generat
Ara Adkins writes:
> I've put a redirect rule on them for now, but given that this is the second
> time that it's happened (as far as I know), is it possible to modify the
> way in which the commit hook sends notifications for new branches with a
> significant history? I don't really know much ab