Just to make this clear it's not my intention to blame anyone or point
fingers.
Given the resources at hand I think Phyx and you have done an amazing job
so far to keep things working!
The core of the issue is that if someone sits down and installs a
"stable" GHC today he
will either get a
Phyx writes:
> Hi Andreas,
>
> GHC 8.6.4 not supporting profiling libs was the first thing mentioned in
> the release email
>
> - A regression resulting in segmentation faults on Windows introduced
>by the fix for #16071 backported in 8.6.3. This fix has been reverted,
>meaning that
Hi Andreas,
GHC 8.6.4 not supporting profiling libs was the first thing mentioned in
the release email
- A regression resulting in segmentation faults on Windows introduced
by the fix for #16071 backported in 8.6.3. This fix has been reverted,
meaning that 8.6.4 is once again susceptible
Hello Devs,
After running into #16408 today I realized there is as of yet no
released bindist
of the 8.6 series which I would consider stable for windows.
GHC 8.6.1 and 8.6.2 had a series of critical bugs which applied to
multiple platforms: https://gitlab.haskell.org/ghc/ghc/issues/16408
GHC
I feel like you didn't read this completely. I used make as the example,
but hadrian is also a build system and will have some version of the same
problem: configure's dependencies are also its outputs. Hadrian might be
able to handle this, if it recomputes the entire dependency tree after
every
On Mon, Mar 18, 2019 at 9:30 PM Ben Gamari wrote:
> Shayne Fletcher via ghc-devs writes:
>
> > Consider this two file program:
> > ```
> > module T where
> > main = undefined
> >
> > module Main where
> > import T
> > main = putStrLn "Hello world!"
> > ```
> >
> > Both 8.4.3 and 8.6.3 agree:
>
On Fri, Mar 15, 2019 at 4:52 PM Brandon Allbery wrote:
> Newcomers to autoconf-based ecosystems often add a rule to run configure
> to their Makefiles, as a "shortcut". At some time thereafter, they discover
> that there's a problem when configure alters the build plan make is
> executing.
Agreed, I was also an opponent of -c as the default, and as you pointed out
it only works for the case where the default is used. But even if the
defaults are used it is still harmful to do it automatically as the user's
environment could have changed resulting in different configure output if
you
