Thank's Arne. I made the changes you suggested to the configure script and everything worked pretty much as it should.
Arne wrote:
" --with-pythondir=/usr/lib64" didn't work for me. Made me do some checking. On 8.3 2005 05:49, Joe Morris (NTM) wrote:
David wrote:
I have exactly the same problem. When I do the ./configure this is on the Python line. ================================= checking for Python directory... /usr/local checking for Python2.3... header /usr/include/python2.3 library no modules no =================================
You need --with-pythondir=/usr/lib64 I had a typo that might be of interest since I have seen the same kind of thing in configure script (hard coded to lib not lib64 directories). There was a typo in my spec file that made the line --with-pythondir=/usr/lib64 /usr instead of just /usr/lib64. If passed
David wrote: that way (i.e. 2 directories), it does find python modules and compiles fine. This might come in handy for other broken configure scripts. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871