[Zope-DB] DCO2 binaries, win32 and Zope 2.7 - deos not work with py2.3.x

Matthew T. Kromer matt at bane.mi.org
Mon May 31 12:46:46 EDT 2004


Just edit the makefile by hand when you see this and make the line that 
reads DEFS=@DEFS@ just read DEFS=


On May 30, 2004, at 3:57 PM, Cynthia Kiser wrote:

> Quoting Dario Lopez-K?sten <dario at ita.chalmers.se>:
>> i am wondering if anyone has been able to compile or otherwise 
>> produce a
>> python 2.3 binary for DCOracle2?
>
> I am similarly having problems compiling DCOracle2 with
> python2.3.3. My system is Linux (RH 7.3) with Python 2.3.3 built from
> source. I have previously built DCOracle2-1.3b on the same machine,
> same Oracle database, but with python 2.1 (installed from a source
> rpm). The relevant portions of the make output are below. If you look
> at the directories from which I am building, it looks like I have
> different DCOracle2 versions but the second one is simply a copy of
> the first because I needed to leave the original DCOracle binary in
> place to use with my Zope 2.6.x servers.
>
> The compilation error with 2.3.3 is:
>
> make || ./builderrors)
> make[1]: Entering directory
> `/its/software/stow/zope-2.7-products/DCOracle2/src'
> gcc -pthread -fPIC -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
> -I/software/bin/../stow/python-2.3.3/include/python2.3
> -I/software/bin/../stow/python-2.3.3/include/python2.3 @DEFS@
> -I/ora/product/8.1.7/rdbms/demo -I/ora/product/8.1.7/network/public
> -I/ora/product/8.1.7/plsql/public -I/ora/product/8.1.7/rdbms/public
> -DORACLE8i -c ././dco2.c -o ./dco2.o
> gcc: cannot specify -o with -c or -S and multiple compilations
> make[1]: *** [dco2.o] Error 1
> make[1]: Leaving directory
> `/its/software/stow/zope-2.7-products/DCOracle2/src'
> 		---------------------------------------
> There were errors building the dco2 module.  This could be because of
> a coding error in the dco2 module, or because your Oracle environment 
> is
> not set up properly.
>
>
> The analogous section from my successful compile is:
>
> make || ./builderrors)
> make[1]: Entering directory
> `/its/software/stow/zope-products/DCOracle2-1.3b/src'
> gcc -fPIC -g -O2 -D_FILE_OFFSET_BITS=64 -DHAVE_LARGEFILE_SUPPORT
> -I/usr/include/python2.1 -I/usr/include/python2.1 -DHAVE_CONFIG_H
> -I/ora/product/8.1.7/rdbms/demo -I/ora/product/8.1.7/network/public
> -I/ora/product/8.1.7/plsql/public -I/ora/product/8.1.7/rdbms/public
> -DORACLE8i -c ././dco2.c -o ./dco2.o
> gcc -shared  ./dco2.o  -L/ora/product/8.1.7/lib/ -lclntsh
> -Wl,-rpath,/ora/product/8.1.7/lib  -o ./dco2.so
> make[1]: Leaving directory
> `/its/software/stow/zope-products/DCOracle2-1.3b/src'
> cp src/dco2.so DCOracle2
>
> I have a suspicion that I need to recompile python, but not sure what
> is wrong with it. I know it seems not to have found some Tcl libraries
> when I made it (probably not related to this problem). But I am
> wondering about the difference in gcc options that configure seems to
> have set for my DCOracle compiles, especially pthread and
> HAVE_LARGEFILE_SUPPORT. I am also wondering why @DEFS@ was not
> substituted in the failed compile. In the successful one, this seems
> to have ended up as HAVE_CONFIG_H.
>
> -- 
> Cynthia Kiser
> cnk at caltech.edu
>
>
>
> _______________________________________________
> Zope-DB mailing list
> Zope-DB at zope.org
> http://mail.zope.org/mailman/listinfo/zope-db




More information about the Zope-DB mailing list