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 jwpye
Recipients
Date 2004-10-22.01:08:25
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=1044177

I understand now:

flaw@void:~ % sudo ldconfig /usr/lib /usr/local/lib
/usr/X11R6/lib /usr/dev/lib
flaw@void:~ % ldconfig -r | grep 'python'
        342:-lpython2.3.1 => /usr/local/lib/libpython2.3.so.1

/usr/dev/lib has libpython2.4.so and libpython2.4.so.1.0

flaw@void:~ % cd /usr/dev/lib
flaw@void:/usr/dev/lib % sudo ln -s libpython2.4.so.1.0
libpython2.4.so.1
flaw@void:/usr/dev/lib % sudo ln -sf libpython2.4.so.1
libpython2.4.so
flaw@void:/usr/dev/lib % l libpython2.4.so
lrwxr-xr-x  1 root  wheel  - 17B Oct 21 18:01
libpython2.4.so -> libpython2.4.so.1
flaw@void:/usr/dev/lib % l libpython2.4.so.1
lrwxr-xr-x  1 root  wheel  - 19B Oct 21 18:01
libpython2.4.so.1 -> libpython2.4.so.1.0
flaw@void:/usr/dev/lib % sudo ldconfig /usr/lib
/usr/local/lib /usr/X11R6/lib /usr/dev/lib
flaw@void:/usr/dev/lib % ldconfig -r | grep 'python'
        342:-lpython2.3.1 => /usr/local/lib/libpython2.3.so.1
        625:-lpython2.4.1 => /usr/dev/lib/libpython2.4.so.1

Although, it doesn't appear to be "fatal". A ld
-L/usr/dev/lib -lpython2.4 will work fine, either way.
History
Date User Action Args
2007-08-23 15:40:11adminlinkissue1044395 messages
2007-08-23 15:40:11admincreate