I can't run Feynman successfully

[clzoc]

cabal.exe: Could not resolve dependencies:
[__0] trying: Feynman-0.1.0.0 (user goal)
[__1] unknown package: old-time (dependency of Feynman)
[__1] fail (backjumping, conflict set: Feynman, old-time)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: Feynman, old-time

Above is the error information. I have used stack to install ghc-8.0.2 and base-4.9.1.0. Whether i install or uninstall the old-time library, it just report these dependency problem above. I used to try the Sandboxes tutorial, but i was trapped in "Downloading the latest package list from hackage.haskell.org".

[meamy]

Sorry for the trouble compiling! I'm guessing old-time isn't included in stack's curated packages. I've been looking to get rid of old-time so I'll try to get that done now which should hopefully solve the problem.

I'm also curious as to why cabal update is failing. If you're on Mac this may be relevant: https://stackoverflow.com/questions/25498161/2014-haskell-cabal-update-hangs-on-mac

[clzoc]

It is my honor to receive such a wonderful response from a brilliant scientist like you. Thank you for your patience. In order to write a Java program with the same function of the haskell project, i am learning your articles and i have get a lot of benefit from them. In fact， i use "stack" to initialize and build the haskell project instead of "cabal" after i open that issue. It seems good at the beginning, i use lts-11.22 and download parsec3-numbers package, all dependency problem disappear, then i input "stack build" and it start to compile, but i fail again. Three text files about my fault have been add to attachment, i guess the windows operating system maybe the problem. Now, i intend to install Linux and try the process. Thank you for your response.  

…

------------------&nbsp;原始邮件&nbsp;------------------ 发件人: "meamy/feynman" <notifications@github.com&gt;; 发送时间:&nbsp;2020年11月17日(星期二) 晚上9:09 收件人:&nbsp;"meamy/feynman"<feynman@noreply.github.com&gt;; 抄送:&nbsp;"刘展欧10151590236"<1055343256@qq.com&gt;;"Author"<author@noreply.github.com&gt;; 主题:&nbsp;Re: [meamy/feynman] I can't run Feynman successfully (#1) Sorry for the trouble compiling! I'm guessing old-time isn't included in stack's curated packages. I've been looking to get rid of old-time so I'll try to get that done now which should hopefully solve the problem. I'm also curious as to why cabal update is failing. If you're on Mac this may be relevant: https://stackoverflow.com/questions/25498161/2014-haskell-cabal-update-hangs-on-mac — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[meamy]

No problem at all! I'm not able to see the files --- would you mind uploading them directly to github? I think the email reply doesn't upload attachments.

Thanks!

[clzoc]

1. stack.yaml
   stack.yaml.txt

2. stack.yaml.lock
   stack.yaml.lock.txt

3. error_report after input stack build
   error_report.txt

[meamy]

It looks like the error report may have been cut off, I'm only seeing warnings (of which feynman generates many).

The latest commit removes the old-time dependency, so that may help. It seems stack doesn't index parsec3-numbers which is a slightly more annoying dependency to remove.

[clzoc]

It is useful. Thank you for your kindness and patience.

[clzoc]

I am happy to run Feynman successfully now. I have installed a Debian Linux system on Oracle VM VirtualBox. After download essential tools and export them to environment PATH, two executable files named 'feynopt' and 'feynver' have been create. Then i was able to operate quantum circuits files such as .qc and .qasm. It is obvious that the problem is depend on Windows system. Maybe it is a simple and stupid problem，but i am really happy to solve it. In addition, i just can't imagine to get your patient response and help, i am grateful for that. In the end, if you agree, i want to close the issue after two days.

[meamy]

Great! Glad to hear you got it working. I'll close this now, though I'll open another issue anyway to remind myself to get stack working.