Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFails to compile with GHC 8.0.2 / LTS 8.1 #1566
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Feb 19, 2017
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Feb 19, 2017
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Feb 19, 2017
Contributor
It's not expected to compile with anything beyond GHC 7.10, see https://github.com/elm-lang/elm-platform/blob/master/installers/BuildFromSource.hs
So this is not a bug report, or unexpected. Elm will start to compile with GHC 8 when Evan decides to switch to that compiler on his development machine. Until then, having this issue here open serves no purpose.
|
It's not expected to compile with anything beyond GHC 7.10, see https://github.com/elm-lang/elm-platform/blob/master/installers/BuildFromSource.hs So this is not a bug report, or unexpected. Elm will start to compile with GHC 8 when Evan decides to switch to that compiler on his development machine. Until then, having this issue here open serves no purpose. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
domenkozar
Feb 20, 2017
I don't think it's an issue because of GHC 8, but rather the newest version of some package.
domenkozar
commented
Feb 20, 2017
|
I don't think it's an issue because of GHC 8, but rather the newest version of some package. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Feb 20, 2017
Contributor
That's well possible. Who knows. But it doesn't make a difference. See #1431 and #1479 and #1488 for a similar story. Unless you can say exactly what the offending package is, and why a newer version should be preferred, and how to accomplish that, your issue will be closed. So I suggest you close it yourself, to save Evan the work.
|
That's well possible. Who knows. But it doesn't make a difference. See #1431 and #1479 and #1488 for a similar story. Unless you can say exactly what the offending package is, and why a newer version should be preferred, and how to accomplish that, your issue will be closed. So I suggest you close it yourself, to save Evan the work. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
domenkozar
Feb 20, 2017
So Evan doesn't care if the software can't be used on the latest stable compiler even if a patch is provided?
domenkozar
commented
Feb 20, 2017
|
So Evan doesn't care if the software can't be used on the latest stable compiler even if a patch is provided? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jvoigtlaender
Feb 20, 2017
Contributor
I can't answer that question. I only pointed you to information that seems relevant to this issue being open.
|
I can't answer that question. I only pointed you to information that seems relevant to this issue being open. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
domenkozar
commented
Feb 23, 2017
|
For the record, it's |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Jul 14, 2017
Member
I will upgrade to a later version of GHC at some point, but it is not a super high priority in the grand scheme of things since getting it installed on Windows, Linux, and Mac to make binaries seems to be quite an ordeal.
That said, maybe there is still something to do in the meantime. I'm not sure what the action item is though, so open a new issue with a specific title and description that suggests a concrete change if that is what you are looking for.
|
I will upgrade to a later version of GHC at some point, but it is not a super high priority in the grand scheme of things since getting it installed on Windows, Linux, and Mac to make binaries seems to be quite an ordeal. That said, maybe there is still something to do in the meantime. I'm not sure what the action item is though, so open a new issue with a specific title and description that suggests a concrete change if that is what you are looking for. |
evancz
closed this
Jul 14, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
h4ck3rm1k3
Dec 9, 2017
@domenkozar what is the patch? I am having the same issue on upgrading the https://github.com/h4ck3rm1k3/haskelm to the latest version of haskell.
h4ck3rm1k3
commented
Dec 9, 2017
|
@domenkozar what is the patch? I am having the same issue on upgrading the https://github.com/h4ck3rm1k3/haskelm to the latest version of haskell. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jerith666
Dec 9, 2017
@h4ck3rm1k3 the commit in NixOS/nixpkgs#22932 is NixOS/nixpkgs@afb7d04. It just pins some dependencies at earlier versions -- it doesn't actually make changes to the elm source code to be compatible with the latest versions.
jerith666
commented
Dec 9, 2017
•
|
@h4ck3rm1k3 the commit in NixOS/nixpkgs#22932 is NixOS/nixpkgs@afb7d04. It just pins some dependencies at earlier versions -- it doesn't actually make changes to the elm source code to be compatible with the latest versions. |
domenkozar commentedFeb 19, 2017
I haven't dug into why, but here's the error: