The above problems were encountered when packaging a stand-alone Python environment. It is mainly caused by the inconsistency between the software execution environment and the compilation environment
That is, the environment in which Python is executed needs to be consistent with the environment in which Python is compiled. Specifically, python packaged under Linux cannot be executed under Mac
It is not easy to distinguish the python compilation environment, except that the official website gives an obvious distinction. In daily cooperation, it is common to lack corresponding documents corresponding to customized Python environment
You can use file program
under Linux or Mac to view the compilation environment of the program.
Similar Posts:
- format not a string literal and no format arguments
- arm-linux-gnueabihf-g++: error trying to exec ‘cc1plus’: execvp: No such file or directory
- [Solved] asp.net core Microsoft.Hosting.Lifetime[0] Application is shutting down…
- How to Solve Airflow Install Error: OSError: [Errno 2] No such file or directory
- The solution of losing vcruntime140.dll in the latest Apache installation
- Syntax error: word unexpected (expect
- [Solved] ldd reports an error: not found (the arm version of gdb is exsited)
- Go to: install C extended compiler environment of Python under windows (solve the problem of “unable to find vcfarsall. Bat”
- python ImportError: No module named yaml
- Error in importing tensorflow in Jupiter Notebook: no module named tensorflow solution