[Zope-DB] DCOracle2 on AIX5.2 -- issues

[Matthew T.Kromer]

It's probably the TRACE macro which is generating a lot of these  
messages, if you don't need to be able to do runtime tracing (for  
diagnostics) then you can tweak the #define TRACE(condition,args) to  
be a no-op macro -- just delete the body of the macro.


On Mar 14, 2006, at 2:54 PM, Dieter Maurer wrote:

> mfmorss at aep.com wrote at 2006-3-13 13:32 -0500:
>> ...
>> However, during compilation of cdo2.o, I did encounter these  
>> symptoms:
>>
>> cc_r -DNDEBUG -O -I/oracle/product/9.2.0.6/rdbms/demo
>> -I/oracle/product/9.2.0.6/network/public -I/oracle/product/9.2.0.6
>> /plsql/public -I/oracle/product/9.2.0.6/rdbms/public
>> -I/oracle/product/8.1.7.2/rdbms/demo -I/oracle/product/8.1.7.2/ 
>> rdbms/public
>> -I/app/sandbox/s625662/installed/include/python2.4 -c src/dco2.c -o
>> build/temp.aix-5.2-2.4/src/dco2.o -brtl -bexpall -DORACLE8i
>> "src/dco2.c", line 5004.38: 1506-280 (W) Function argument assignment
>> between types "unsigned long*" and "long*" is not allowed.
>> "src/dco2.c", line 6066.25: 1506-068 (W) Operation between types  
>> "short*"
>> and "unsigned short*" is not allowed.
>> "src/dco2.c", line 6109.25: 1506-068 (W) Operation between types  
>> "short*"
>> and "unsigned short*" is not allowed.
>
> Obviously, your compiler does not like thing (to be precise:
> the implicit conversion between "short" and "unsigned short")
> that the author did not expect to hurt compilers (and which
> most compilers accept).
>
> Your options:
>
>   *  use a different (less strict) compiler
>
>   *  fix the code (such that even your strict compiler feels happy).
>
> -- 
> Dieter
> _______________________________________________
> Zope-DB mailing list
> Zope-DB at zope.org
> http://mail.zope.org/mailman/listinfo/zope-db