Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CMakeLists.txt hardcodes Python version 3.6 #169

Closed
laurynas-biveinis opened this issue Apr 10, 2019 · 6 comments
Closed

CMakeLists.txt hardcodes Python version 3.6 #169

laurynas-biveinis opened this issue Apr 10, 2019 · 6 comments

Comments

@laurynas-biveinis
Copy link

On macOS, with latest Homebrew Python, which is 3.7:
$ cmake ...
(no issues nor any Python-related output)
$ make
...
[ 1%] Generating timestamp
make[2]: PYTHON-NOTFOUND: No such file or directory

This appears to be caused by https://github.com/trailofbits/deepstate/blob/master/CMakeLists.txt#L59 hardcoding "python3.6" as executable name to search for. Naturally, this fails to find python3.7. Editing the line to "python3" allows the build to complete

@ggrieco-tob
Copy link
Contributor

The current master branch is (kind of) broken, since we had only partial python3 support. Sorry! I promise I will fix this soon (and this issue as well).

@laurynas-biveinis
Copy link
Author

@ggrieco-tob, is there a known good branch/tag/commit hash I could use currently for work along the lines of https://blog.trailofbits.com/2019/01/22/fuzzing-an-api-with-deepstate-part-1/ (i.e. simple proof-of-concept ADT fuzzing?)

(on a related note to the original report, README.md still lists Python 2 as a dependency)

@ggrieco-tob
Copy link
Contributor

Yes!, 4dfd951 from master should work.

@ggrieco-tob
Copy link
Contributor

Also, if you want direct support (or to discuss new ideas!) about DeepState, don't forget to join the #deepstate channel in the Empire Hacking slack. 😄

@ggrieco-tob
Copy link
Contributor

This should be fixed now. Thanks!

@laurynas-biveinis
Copy link
Author

Confirmed. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants