...
1) To get the compiled Python to run independently, I have to hack >LD_LIBRARY_PATH to get it to execute. `LD_LIBRARY_PATH=./Python-3.11.1 >./Python-3.11.1/python` .
Even when trying to execute from the same
directory as the binary & executable, I get an error, `/python: error
while loading shared libraries: libpython3.11.so.1.0: cannot open shared >object file: No such file or directory`.
2) When running the C++ program that embeds Python, I see these messages >after initializing:
`Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>`
This is seemingly connected to some issues regarding libraries: When I
run the Python interpreter directly, I can get some of the way through
the process of creating a virtual environment, but it doesn't seem to
leave me with a working pip:
`$ LD_LIBRARY_PATH=./Python-3.11.1 ./Python-3.11.1/python
subprocess.CalledProcessError: Command >'['/home/john/Development/7DRL/cpp_embedded_python/venv/bin/python',import venv
venv.create("./venv", with_pip=True)
'-m', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit >status 127.`
...
3) I'm not sure I even need to be statically linking the interpreter.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 70:42:32 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,356,842 |