Re: cannot build python bindings on suse 10.2

--- In [email protected], Brandon Long <blong@...> wrote:
>
> On 08/30/07 mandy_roemer uttered the following other thing:
> > --- In [email protected], Brandon Long <blong@> wrote:

Brandon i found it out:
I downloaded now Python 2.2.3 to my SuSE 10.2 machine, compiled and 
installed them. GCC is the normaly installed by SuSE (4.2.1).

And if i now got to the /clearsilver-0.10.5/python dir after 
compiling cleasilver and do a "python setup.py install" it works!!!

Now the Python bindings are installed correctly see here:
---
poldi:/usr/local/src/clearsilver-0.10.5/python # python setup.py 
install
adding lib_path $(LIB_DIR)
adding lib z
running install
running build
running build_ext
building 'neo_cgi' extension
skipping neo_cgi.c (build/temp.linux-i686-2.2/neo_cgi.o up-to-date)
skipping neo_cs.c (build/temp.linux-i686-2.2/neo_cs.o up-to-date)
skipping neo_util.c (build/temp.linux-i686-2.2/neo_util.o up-to-date)
creating build/lib.linux-i686-2.2
gcc -shared build/temp.linux-i686-2.2/neo_cgi.o build/temp.linux-
i686-2.2/neo_cs.o build/temp.linux-i686-2.2/neo_util.o -L../libs/ -
L../libs -lz -lneo_cgi -lneo_cs -lneo_utl -o build/lib.linux-i686-2.2/
neo_cgi.so
running install_lib
copying build/lib.linux-i686-2.2/neo_cgi.so -> /usr/lib/python2.2/
site-packages
---


> > >
> > > *sigh*
> > > 
> > > Ok, so this is caused by incompatibilities between how the 
> > clearsilver
> > > libraries are built, and how python was originally built.
> > > 
> > Maybe its about gcc 4.1 on SuSE.
> > I wrote this:
> > 
> > GCC 4.1,
> > GCC 4.2: There is a known incompatibility between Python and GCC,
> >          where GCC 4.1 and later uses an interpretation of C 
> >          different to earlier GCC releases in an area where the C 
> >          specification has undefined behaviour (namely, integer 
> > arithmetic 
> >          involving -sys.maxint-1).
> > 
> >          As a consequence, compiling Python with GCC 4.1/4.2 is 
not
> >          recommended. It is likely that this problem will be 
resolved
> >          in future Python releases. As a work-around, it seems 
that
> >          adding -fwrapv to the compiler options restores the 
earlier
> >          GCC behaviour.
> > 
> > so what should i do now??
> 
> Yeah, I don't think that matters.
> 
> Brandon
> -- 
>   "If you do have a computer and e-mail, you probably have already
>      been taken to the cleaners by Microsoft."
>                   http://groups.yahoo.com/group/0xdeadbeef/
message/2307
>