pyme-help

Re: [Pyme-help] Problem with building PyMe

[Igor B. <be...@us...>]

Nima,

First, I think it's not a good reason to switch between Linux 
distributions just because you have such a small problem. I could only 
hope that you will find more of them latter on. ;-)

As for the problem itself, I'd like to know more regarding how did you 
do the build and in what environment since there's no dependency on 
apache in the pyme package whatsoever.

Looking though my Google query hits reveals that _apache is a module 
loaded by Apache when it runs. It sounds a little bit strange that you 
would get that during build of the pyme. What command you run (and 
where) to do the build? Are you sure you see the problem during build 
and not while running a script using it?

I'm also slightly surprised to see python2.5 to be in /usr/local/lib. 
I'm not quite familiar with openSUSE details but is it where the 
official install puts it or did you do installation of some packages on 
your own? If the latter - which of the Apache, mod_python, and Python2.5 
did you installed yourself? Did you verified that their installation was 
successful?

Cheers,
Igor

Nima wrote:
> Message body follows:
>
> Dear Igor,
>
> I have a project I want to setup and use and it is written
> in python and it has a lot of dependencies. I use apache
> Apache/2.2.4 with mod_python/3.3.1 using Python 2.5 on
> openSUSE linux 10.2.
> Unfortunately being a novice in python and linux both are
> bothering me;
>
> 1) I tried building PyMe-0.7.0 and I got this message:
>
>   File "server.py", line 37, in <module>
>     from mod_python import apache
>   File
> "/usr/local/lib/python2.5/site-packages/mod_python/apache.py",
> line 30, in <module>
>     import _apache
> ImportError: No module named _apache 
>   File "server.py", line 37, in <module>
>     from mod_python import apache
>   File
> "/usr/local/lib/python2.5/site-packages/mod_python/apache.py",
> line 30, in <module>
>     import _apache
> ImportError: No module named _apache
>
> I tried rebuilding SWIG and gpgme and no changes.
> What do you suggest me to do ? Do you think it has to do
> with the distribution of my linux ? Should I move to debian?
>
> It would be nice of you to help me on this matter, 
>
> Warmest regards,
> Nima
>   

Re: [Pyme-help] Problem with building PyMe

[Igor B. <be...@us...>]

Nima Dokoohaki wrote:
> My mistake, I think I gave you wrong info, I copy/pasted that from my 
> previous emails Igor,
> It has nothing to do with apache. I solved the problem of _apache, It 
> had to do with configurations.
> I moved the directive to main config and it seems ok now with apache 
> for me.
> unfortunately I get this error while installing , and during the 
> script run i get "no module named pyme"
>
> Well, I run the command " Python setup.py install " ;
> linux-station:/home/nima/pyme-0.7.0 # python setup.py install
> running install
> running build
> running build_py
> running build_ext
> building 'pyme._gpgme' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall 
> -Wstrict-prototypes -fPIC -I/home/nima/pyme-0.7.0 
> -I/usr/local/include/python2.5 -c gpgme_wrap.c -o 
> build/temp.linux-i686-2.5/gpgme_wrap.o -I/usr/local/include
> gcc: gpgme_wrap.c: No such file or directory
> gcc: no input files
> error: command 'gcc' failed with exit status 1
This error means that you didn't run SWIG on gpgme files first. The 
correct way would be to run 'make install' which makes all necessary 
build steps. If you want details you can look in the Makefile which 
controls what 'make' does but in short it preprocesses gpgme.h using a 
short python script and generates gpgme_wrap.c using swig before 
building the pyme module itself.

Hope it helps,
Igor