-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MA: Made changes that leave me with a broken Agda system; please help.
- Loading branch information
Musa Al-hassy
committed
Oct 2, 2018
1 parent
cf921d3
commit 6043e77
Showing
6 changed files
with
210,390 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
mmodule silly1 where | ||
|
Oops, something went wrong.
2 comments
on commit 6043e77
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Makefile installs the current Agda as agda-2.6.0
, see issue agda#3154. You might have two versions of Agda installed now, agda
and agda-2.6.0
which gives you the confusing behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, it seems I only have one resulting agda
--no version number attached to anything.
Is the problem perhaps that the file that defines the Agda primitives (probably
/home/alhassy/.cabal/share/x86_64-linux-ghc-8.0.2/Agda-2.6.0/lib/prim/Agda/Primitive.agda
) still has amodule
line, not ammodule
line? If so, maybe experiment withrrecord
instead?