That libpython3.4m.so doesn’t resolve indicated LD_RUN_PATH wasn’t set 
correctly when the build was done.

Can you make sure again that you ran the commands as:

    make distclean
    ./configure --with-apxs=/opt/rh/httpd24/root/usr/bin/apxs 
--with-python=/opt/rh/rh-python34/root/usr/bin/python3.4m
    LD_RUN_PATH=/opt/rh/rh-python34/root/lib64 make

Then run that ldd command again:

    LD_LIBRARY_PATH='' ldd src/server/.libs/mod_wsgi.so

To confirm that the library is in the location, what do you get for:

    ls -las /opt/rh/rh-python34/root/lib64

Also, what are the values of LDFLAGS and LDLIBS in the Makefile generated by 
configure step?

Graham

> On 11 May 2016, at 3:43 AM, Chanki Gogia <[email protected]> wrote:
> 
> Hi Graham,
> 
> The command 
> LD_LIBRARY_PATH='' ldd src/server/.libs/mod_wsgi.so
> gives:
> linux-vdso.so.1 => (0X00007ffcfd78d000)
> libpython3.4m.so.rh-python34-1.0 => not found
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f934a5e9000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f934a3e5000)
> libutil.so.1 => /lib64/libutil.so.1 (0x00007f934a1e2000)
> libm.so.6 => /lib64/libm.so.1 (0x00007f9349edf000)
> libc.so.6 => /lib64/libc.so.1 (0x00007f9349b1e000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f934aa53000)
> 
> Should I try :
> $LD_LIBRARY_PATH = /opt/rh/rh-python34/root/lib64/
> 
> Acc. to 
> http://stackoverflow.com/questions/7880454/python-executable-not-finding-libpython-shared-library
>  
> <http://stackoverflow.com/questions/7880454/python-executable-not-finding-libpython-shared-library>
> 
> Thanks,
> Chanki
> 
> On Tuesday, May 10, 2016 at 3:38:06 AM UTC+5:30, Graham Dumpleton wrote:
> 
>> On 10 May 2016, at 12:28 AM, Chanki Gogia <[email protected] <>> wrote:
>> 
>> Hi Graham,
>> 
>> I apologize for using screenshots !
>> I had done that before with "make clean" , now had tried again with "make 
>> distclean" but similar result.
>> 
>> Below is the complete first line of make, Last 3 lines are worth note :
>> 
>> /opt/rh/httpd24/root/usr/bin/apxs -c 
>> -I/opt/rh/rh-python34/root/usr/include/python3.4m -DNDEBUG -D_GNU_SOURCE 
>> -Wc,-g -Wc,-02 src/server/mod_wsgi.c src/server/wsgi_*.c 
>> -L/opt/rh/rh-python34/root/usr/lib64 
>> -L/opt/rh/rh-python34/root/usr/lib64/python3.4/config-3.4m -lpython3.4m 
>> -lpthread -ldl -lutil -lm /usr/lib64/apr-1/build/libtool --silent 
>> --mode::compile gcc -std:gnu99 -prefer-pic -02 -g -pipe  -Wall 
>> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong 
>> -param::ssp-buffer-size::4 -grecord-gcc-sitches -m64 -mtune::generic -DLINUX 
>> -D_REENTERANT -D_GNU_RESOURCE -pthread 
>> –I/opt/rh/httpd24/root/usr/include/httpd –I/usr/include/apr-1  
>> -I/usr/include/apr-1 -g -02 
>> -I/opt/rh/rh-python34/root/usr/include/python3.4m -DNDEBUG  -D_GNU_SOURCE -c 
>> -o src/server/mod_wsgi.lo src/server/mod_wsgi.c&& touch 
>> src/server/mod_wsgi.slo
>> src/server/mod_wsgi.c: In function ‘wsgi_process_proxy_headers’:
>> src/server/mod_wsgi.c:12992:25: warning: variable ‘value’ set but not used 
>> [-Wunused-but-set-variable]
>>      const char *value = NULL;
>> After that some other files compile and it ends and then I used make install
>> 
>> LD_LIBRARY_PATH=ldd src/server/.libs/mod_wsgi.so 
> 
> That isn’t the command I gave. It was:
> 
> LD_LIBRARY_PATH='' ldd src/server/.libs/mod_wsgi.so
> 
> Immediately after the ‘=‘ are two quotes to form an empty string for the 
> variable. Alternatively run:
> 
> unset LD_LIBRARY_PATH
> ldd src/server/.libs/mod_wsgi.so
> 
>> gives:
>> Segmentation fault (core dumped)
>>                         
>> Thanks,
>> Chanki
>>                      
>> 
>> On Monday, May 9, 2016 at 1:40:37 PM UTC+5:30, Graham Dumpleton wrote:
>> Unless you started from fresh source code, forgot one important step. 
>> 
>> Before you rerun configure/make, ensure you run: 
>> 
>>     make distclean 
>> 
>> This will clear out previously compiled files. Without that it would have 
>> just reused the previous object which had been compiled. 
>> 
>> Once you have done it all again, try doing the following: 
>> 
>> LD_LIBRARY_PATH='' ldd src/server/.libs/mod_wsgi.so 
>> 
>> from in the mod_wsgi source directory. 
>> 
>> What does this output? 
>> 
>> Do not send screen shots as images. Sending images is the quickest way to 
>> ensure people will not help you. Send as text instead. 
>> 
>> > On 9 May 2016, at 5:33 PM, Chanki Gogia <chank...@ <>gmail.com 
>> > <http://gmail.com/>> wrote: 
>> > 
>> > Thanks, 
>> > I tried the above but again couldn't load module successfully. Same error. 
>> > If you could please have a look at attached file- mod_wsgi_make.jpg , I 
>> > guess mod_wsgi.slo doesn't creates and failing with error mentioned in the 
>> > image attached earlier(mod_wsgi_make.jpg) 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google Groups 
>> > "modwsgi" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send an 
>> > email to modwsgi+u...@ <>googlegroups.com <http://googlegroups.com/>. 
>> > To post to this group, send email to mod...@ <>googlegroups.com 
>> > <http://googlegroups.com/>. 
>> > Visit this group at https://groups.google.com/group/modwsgi 
>> > <https://groups.google.com/group/modwsgi>. 
>> > For more options, visit https://groups.google.com/d/optout 
>> > <https://groups.google.com/d/optout>. 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "modwsgi" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <>.
>> To post to this group, send email to [email protected] <>.
>> Visit this group at https://groups.google.com/group/modwsgi 
>> <https://groups.google.com/group/modwsgi>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "modwsgi" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at https://groups.google.com/group/modwsgi 
> <https://groups.google.com/group/modwsgi>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to