This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author salgerman
Recipients eric.smith, salgerman, zach.ware
Date 2022-02-09.03:06:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644375964.09.0.110313547538.issue46683@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2022-02-09 03:06:04salgermansetrecipients: + salgerman, eric.smith, zach.ware
2022-02-09 03:06:04salgermansetmessageid: <1644375964.09.0.110313547538.issue46683@roundup.psfhosted.org>
2022-02-09 03:06:04salgermanlinkissue46683 messages
2022-02-09 03:06:03salgermancreate