Closed onionhammer closed 11 years ago
Sorry didnt see your comment til now. I'm just killing time at the moment but I've run out. I'll merge them later.
Hey, if you're getting compile errors, it's recommended you build nimrod from the github version Araq/Nimrod, rather than using the release off the nimrod website.
Not compile errors. A bunch of my changes are getting reversed with this PR. For example, writing result.json and iterations support
I was referring to your commit regarding 1e9
nimrod: get it compiling (error with 1e9) and add nimcache to .gitignore
Oh ok... how easy is it to compile nimrod from source? I am thinking ahead to the actual benchmark run
It's pretty easy; if you need any help anyone on freenode #nimrod can help you. I'm on there most days.
The directions are here: https://github.com/Araq/Nimrod
$ git clone git://github.com/Araq/Nimrod.git $ cd Nimrod $ git clone --depth 1 git://github.com/nimrod-code/csources $ cd csources && ./build.sh $ cd .. $ bin/nimrod c koch $ ./koch boot -d:release
Thanks a tonne
Hey, your last commit contains main.exe and main.nim.bak
Blah oops.
Sorry for being a bother, but merging this in will permanently add main.exe to the "history" of the repo, even if you have deleted it with a newer commit
My reco:
Meh, I'll probably just nuke this repo and re-fork from your latest.
Closing this as we have merged the changes in via a separate PR #27
Hey, thanks for the change... I had a bunch of changes in upstream to get the nimrod version to behave the same way as the other versions. They are getting removed with these commits
Could you please get your commits rebased on upstream?