German Salazar <salger...@gmail.com> added the comment:
So, help me understand, please. if I use "--enable-shared": the build produces a rather small python executable; but, the build produces a dynamic library, too and the path to the dynamic library must be included into LD_LIBRARY_PATH for the python executable to work correctly. if I do NOT use "--enable-shared" the build produces a larger python executable; and, it does not produce a dynamic library, but it produces an static library. Does this mean that I do not have to worry about setting up LD_LIBRARY_PATH? In the non-shared, static case, I thought the static library would be inside the executable, but, funny enough, I noticed that the python executable is smaller than the static library, so...I am confused. I would like to have 3.6, next to 3.7 and 3.8 with minimal setup, thus the static route. Please advise. ---------- components: +Installation resolution: not a bug -> status: closed -> open type: -> behavior _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46683> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
