control: forcemerge 871740 867853
> Okay, I'll take this to mean that if I submit a working/useful patch, you'll
> apply it. I'll get to work on that.
consider that: gcc-5 is not part of any Debian stable release, and gcc-4.9 is
has been part of jessie for a while, but
jessie was released
On Mon, 10 Jul 2017 16:50:03 + (UTC)
Gianfranco Costamagna wrote:
> updating control file, adding version constraints with versions not in the >
> archive anymore is kind of useless, speaking about Buster we won't have suc
> gcc versions anymore since at least two
Hello,
>I'm not sure I understand this response.
>
>When you say "gcc-specific", are you saying that the Debian Haskell package
>supports compilers other than gcc? It appears to me that it specifically
>requires gcc.
I mean, that the flag has been added by gcc, and a lot of programs in
> I guess it is better to patch older gccs to understand such flag and give
> no-op in this case.
> There is no point in:
> 1) fixing the whole archive for a gcc-specific change
> 2) using ghc with older, unsupported compilers.
I'm not sure I understand this response.
When you say "gcc-specific",
Package: ghc
Version: 8.0.1-17
Severity: important
The ghc package needs tighter dependencies against gcc and gcc-5 :
When I'm using old versions of gcc, I get the following error message when
ghc tries to do the link phase:
Linking test ...
gcc: error: unrecognized command line option