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

Binary with the name "python" required #6

Open
s9105947 opened this issue Apr 15, 2021 · 1 comment
Open

Binary with the name "python" required #6

s9105947 opened this issue Apr 15, 2021 · 1 comment

Comments

@s9105947
Copy link
Contributor

When the current environment holds no binary python, the build crashes at compilation time. (See full log below)

Note: Maybe this issue should be moved to the firestarter repo, I don't know if this is still an issue upstream.

This is a problem for the more recent versions of debian, which only have a python3 binary, as the binary python has always referred to version 2.7 in that context.

Workaround: start from python virtual environment

Fix: Detect/Configure the python binary path correctly and incorporate python3

[  3%] Create FIRESTARTER source code directory
[  7%] Generate FIRESTARTER source code
/usr/bin/env: 'python': No such file or directory
make[2]: *** [CMakeFiles/libfirestarter.dir/build.make:136: firestarter/Makefile] Error 127
make[1]: *** [CMakeFiles/Makefile2:314: CMakeFiles/libfirestarter.dir/all] Error 2
make: *** [Makefile:160: all] Error 2
@bmario
Copy link
Member

bmario commented Apr 15, 2021

Luckily, the new FIRESTARTER should solve this problem, but please don't use your time on that.

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