Some neuance that perhaps should be included in the README. about evm-semantics

[ehildenb]

We'll include these fixes in the cleanup PR that we have open. I think we've addressed the issues with pandoc-tangle, libxml2-utils, and have a fix in the works for the K versioning. Can you checkout the cleanup branch and let me know if it addresses your issues?

[barrywhitehat1]

With the updated branch I get

formalMethods/evm-semantics$  export PATH=~/ether/formalMethods/pandoc-tangle/bin:$PATH
formalMethods/evm-semantics$  export PATH=~/ether/formalMethods/k/bi:$PATH
Display all 127 possibilities? (y or n)
formalMethods/evm-semantics$  export PATH=~/formalMethods/k/bin:$PATH
formalMethods/evm-semantics$ ./Build run KRYPTO.ml 
== Using uiuck
== kompile: .build/uiuck/ethereum-kompiled/extras/timestamp
== running: KRYPTO.ml
-:1: parser error : Start tag expected, '<' not found
FATAL: Don't know how to set 'krun_opts' for 'KRYPTO.ml'
^

Or similarly with

formalMethods/evm-semantics$ ./Build run *
== Using uiuck
== kompile: .build/uiuck/ethereum-kompiled/extras/timestamp
== running: analysis.md
-:1: parser error : Start tag expected, '<' not found
FATAL: Don't know how to set 'krun_opts' for 'analysis.md'
^

[ehildenb]

If you do ./Build run *, then the * gets interpreted by Bash as globbing (hence it picking up the file analysis.md). See next comment.

[ehildenb]

But doing ./Build run should only be done for a specific file, eg. ./Build run tests/VMTests/vmArithmeticTest/add0.json. Should do something like ./Build test-all to run all the tests (if that's what you're trying to do). Run ./Build help to see the list of available tests.

[ehildenb]

Closing because the latest PR include documentation about this.
Feel free to re-open if you feel it's not sufficient.