ls -ltr /usr/local/lib

-r-xr-xr-x     1 root root  4806649 Nov 11 11:22 libpython2.5.a
-r-xr-xr-x     1 root root  4806649 Nov 12 12:49 libpython2.5.so.1.0
lrwxrwxrwx  1 root root            19 Nov 12 12:49 libpython2.5.so ->
libpython2.5.so.1.0

echo $LD_LIBRARY_PATH

/usr/local/lib

ldd /usr/local/bin/python

        libpython2.5.so.1.0 => /usr/local/lib/libpython2.5.so.1.0
(0x00002b6d8efc5000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00000039a4a00000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00000039a4600000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00000039b3400000)
        libm.so.6 => /lib64/libm.so.6 (0x00000039a4200000)
        libc.so.6 => /lib64/libc.so.6 (0x00000039a3e00000)
        /lib64/ld-linux-x86-64.so.2 (0x00000039a2c00000)

recompile mod_python and do ldd /usr/local/apache2/modules/
mod_python.so

        libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b74c34f7000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00002b74c3711000)
        libutil.so.1 => /lib64/libutil.so.1 (0x00002b74c3915000)
        libm.so.6 => /lib64/libm.so.6 (0x00002b74c3b19000)
        libc.so.6 => /lib64/libc.so.6 (0x00002b74c3d9c000)
        /lib64/ld-linux-x86-64.so.2 (0x00000039a2c00000)

I still don't get why the library is being compiled in statically.

On Nov 13, 12:11 am, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> On Nov 12, 11:44 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
>
>
>
> > echo '/usr/local/lib' >> /etc/ld.so.conf
>
> > more /etc/ld.so.conf
>
> > include ld.so.conf.d/*.conf
> > /usr/local/lib
>
> > ldd /usr/local/bin/python
>
> >         libpython2.5.so.1.0 => not found
> >         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000039a4a00000)
> >         libdl.so.2 => /lib64/libdl.so.2 (0x00000039a4600000)
> >         libutil.so.1 => /lib64/libutil.so.1 (0x00000039b3400000)
> >         libm.so.6 => /lib64/libm.so.6 (0x00000039a4200000)
> >         libc.so.6 => /lib64/libc.so.6 (0x00000039a3e00000)
> >         /lib64/ld-linux-x86-64.so.2 (0x00000039a2c00000)
>
> Where is libpython2.5.so installed? What are the permissions on it?
>
> What do you get for:
>
>   echo $LD_LIBRARY_PATH
>
> just prior to running 'ld'?
>
> Graham
>
> > On Nov 12, 11:57 am, marco ghidinelli <[EMAIL PROTECTED]> wrote:
>
> > > On Wed, Nov 12, 2008 at 03:22:02AM -0800, huw_at1 wrote:
>
> > > > An update on this.
>
> > > > 'which python' returns:
>
> > > >         libpython2.5.so.1.0 => not found
> > > >         libpthread.so.0 => /lib64/libpthread.so.0 (0x00000039a4a00000)
> > > >         libdl.so.2 => /lib64/libdl.so.2 (0x00000039a4600000)
> > > >         libutil.so.1 => /lib64/libutil.so.1 (0x00000039b3400000)
> > > >         libm.so.6 => /lib64/libm.so.6 (0x00000039a4200000)
> > > >         libc.so.6 => /lib64/libc.so.6 (0x00000039a3e00000)
> > > >         /lib64/ld-linux-x86-64.so.2 (0x00000039a2c00000)
>
> > > > This explains why I cannot compile mod_python without first setting
> > > > the LD_LIBRARY_PATH to '/usr/local/lib'. I don't know if this is the
> > > > reason why the mod_python compilation continuously compiles with the
> > > > python library as static. I upgraded my apache to the latest version
> > > > however I still am getting segmentation faults on user authentication.
> > > > Which potentially suggests that the problem is not apache and is
> > > > something else like this issue.
>
> > > echo '/usr/local/lib' >> /etc/ld.so.conf
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to