[ python-Bugs-1575803 ] Missing notice on environment setting LD_LIBRARY_PATH

[SourceForge.net]

Bugs item #1575803, was opened at 2006-10-12 11:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1575803&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Anastasios Hatzis (ahatzis)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing notice on environment setting LD_LIBRARY_PATH

Initial Comment:
Probably it would be a good idea to provide Linux noobs
like me a short notice in the README that
LD_LIBRARY_PATH needs to be set. It was time-consuming
to find out what caused problems with my installation
although the build process went fine.

I don't know if this is really only necessary if Python
is built from source with the "--enable-shared" option.
If yes, a short notice in this paragraph would be fine:

<snip>
Building a shared libpython
---------------------------

Starting with Python 2.3, the majority of the
interpreter can be built
into a shared library, which can then be used by the
interpreter
executable, and by applications embedding Python. To
enable this feature,
configure with --enable-shared.

If you enable this feature, the same object files will
be used to create
a static library.  In particular, the static library
will contain object
files using position-independent code (PIC) on
platforms where PIC flags
are needed for the shared library.
</snip>

Otherwise, if the setting is necessary whether
"--enable-shared" is turned on or off, a good place
would be right after the "make install" explanations.

Again, this is a Linux rookie issue. But if I want to
install the most recent Python version I can't take any
ready-to-use RPM, so I have to build from sources and
will run into these problems the first time.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1575803&group_id=5470