[cx-oracle-users] RE: gcc296 error when building cx_Oracle

[Henning v. B. <H.v...@t-...>]

> Date: Thu, 30 Mar 2006 11:22:05 -0800
> From: "Molina, Gerardo" <Ger...@sc...>
>
> I'm getting the following error when trying to build=20
> cx_Oracle 4.1.2 on Red Hat linux:
>=20
> Linux s0051cdc 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02 EST 2004 i686
> s0051cdc:SQLNET(/opt/ORACLE/TAR/python/cx_Oracle-4.1.2)->pytho
> n setup.py
> build
> running build
> running build_ext
> building 'cx_Oracle' extension
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
> -Wstrict-prototypes -fPIC
> -I/opt/ORACLE/app/oracle/product/9.2.0/rdbms/demo
> -I/opt/ORACLE/app/oracle/product/9.2.0/rdbms/public
> -I/opt/ORACLE/app/oracle/product/9.2.0/network/public
> -I/opt/ORACLE/app/oracle/product/9.2.0/sdk/include
> -I/opt/ORACLE/python/include/python2.4 -c cx_Oracle.c -o
> build/temp.linux-i686-2.4/cx_Oracle.o -DBUILD_TIME=3D3D"March 30, 2006
> 14:17:56"
> gcc2.96 will be used ...
>
> gcc296: cannot specify -o with -c or -S and multiple compilations
> error: command 'gcc' failed with exit status 1
>=20
> Has anyone seen this before? and have a fix?
>
> Thanks in advance,
> Gerardo

Gerardo, I had a similar problem when I tried to build cx_Oracle
as a static extension for python on HP/UX.

In my case it was a problem with the quotation marks in the define
directive for BUILD_TIME - these scrambled the invoked shell somehow.

Here's my workaround: Don't use a DEFINE for BUILD_TIME at all
 and instead hard-code it (I know that's ugly, but it works at least).

- Remove any occurences for BUILD_TIME in the build scripts.
- Modify the file cx_Oracle.c (line 421):
OLD:            PyString_FromString(BUILD_TIME)) < 0)
NEW:            PyString_FromString("February 03, 2006 15:32:22")) < 0)

If you understand German, I can send you a Word-Document by private =
mail.

HTH

Henning

P.S. Anthony, is itpossible for you to solve this in a more general way?
 Or (perhaps even better): Let the Python Build-Gurus change the way
 define directives in "makesetup.local" and "makesetup" are handled?
 It really seems to be a problem with the shell invoked.

=20
 It seems to be a problem everytime