On Sunday, March 3, 2013 12:09:46 PM UTC+5:30, Sarbjit singh wrote: > On Sunday, March 3, 2013 11:53:50 AM UTC+5:30, Benjamin Kaplan wrote: > > > On Sat, Mar 2, 2013 at 10:14 PM, Sarbjit singh <sarbjit1...@gmail.com> > > wrote: > > > > > > > > > > > > > > I searched on google and found these errors could be due to missing > > > python header files which would be available in development package. > > > > > > > > > > > > > > So I am struggling to make it work. > > > > > > > > > > > > > > > > > > A "development package" is meaningless when you aren't installing it > > > > > > from a package. Debian's binary packages don't include the header > > > > > > files, so they put them in a different package. Since you compiled > > > > > > from source, you already have the header files. Did you include the > > > > > > directory you installed Python into on your library and includes > > > > > > paths? > > > > Yes, I configured the makefile for mod_wsgi as without any error : > > > > ./configure --prefix=/opt/lampp/ --with-apxs=/opt/lampp/bin/apxs > --with-python=/opt/lampp/python/bin/python2.7 > --with-mutex-dir=/opt/lampp/var/run/wsgi
Also my LD_LIBRARY_PATH does have path as : /opt/lammp/python/lib Just one more point, while initially I was trying to compiling the mod_wsgi, I was getting error for "libpython2.7.1.0.so Shared library error". I resolved it by creating a soft link to this file in my /usr/lib and /usr/lib64. At that point also my LD_LIBRARY_PATH was having path for python lib but was resolved with soft link only. -- http://mail.python.org/mailman/listinfo/python-list
