[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Oracle |
Notice: | For product status see topics: UNIX 1008, OpenVMS 1009, NT 1010 |
Moderator: | EPS::VANDENHEUVEL |
|
Created: | Fri Aug 10 1990 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1574 |
Total number of notes: | 4428 |
1529.0. "Pro*C 2.0/Oracle 7.2.3/DU 4.0B" by HGOVC::NANDAN () Thu Mar 13 1997 20:08
We are encountering a problem with Pro*C 2.0 and DIGITAL UNIX
4.0B. The version of Oracle is 7.2.3. The patch no 397548 has
already been applied.
We are unable to do the precompilation even with the sample
program. This is an already observed problem as reported in note
no 1369. But the subsequent developments on the solution have not
been reported in that note, so I am posting the problem afresh.
DU 4.0A has been around for quite some time now & DU 4.0B is not
exactly so very new. Is anyone aware of the patch no or a solution
for this problem.
By the way, the application works fine with the same versions of
Oracle and DU 3.2G.
Thanks in advance.
Nandan.
--------------------------------------------------------------------------------
make -f /disk1/oracle/proc/lib/proc.mk ireclen=132 oreclen=132
include=/disk1/oracle/sqllib/public OBJS=sample1.o EXE=sample1 build
/disk1/oracle/bin/proc iname=sample1.pc
Pro*C/C++: Release 2.1.3.0.0 - Production on Thu Mar 13 12:03:52 1997
Copyright (c) Oracle Corporation 1979, 1994. All rights reserved.
System default option values taken from: /disk1/oracle/proc/pmscfg.h
Parser error at line 293, column 25, file /usr/include/sys/types.h:
long _Pfield(valid);
......................................1
(1) PCC-F-02209, Macro invocation has incorrect number of arguments
Parser error at line 294, column 25, file /usr/include/sys/types.h:
char* _Pfield(name);
......................................1
(1) PCC-F-02209, Macro invocation has incorrect number of arguments
Syntax error at line 293, column 25, file /usr/include/sys/types.h:
long _Pfield(valid);
......................................1
(1) PCC-S-02201, Encountered the symbol ";" when expecting one of the following:
: ( * const, double, float, int, long, signed, unsigned,
volatile, an identifier,
Syntax error at line 0, column 0, file sample1.pc:
(1) PCC-S-02201, Encountered the symbol "<eof>" when expecting one of the
following:
; : an identifier, end-exec, random_terminal
(1) PCC-F-02102, Fatal error while doing C preprocessing
*** Exit 1*** Exit 1
--------------------------------------------------------------------------------
T.R | Title | User | Personal Name | Date | Lines |
---|
1529.1 | Pro*C | AXPBIZ::RANJAN | | Fri Mar 14 1997 10:43 | 2 |
| I'm not sure what the Pro*C patch contains, but just curious whether you are
using the code=ansi_c option during pre-compilation.
|
1529.2 | Bug 409906 | HGOVC::NANDAN | | Sat Mar 15 1997 04:13 | 22 |
|
The patch 397548 consists of the following files - sf.o, sm.o,
ssf.o, uitl.o & I think only the 'oracle' and 'svrmgr' files are
built by the patch.
To answer your question, I do not think we are using the 'code'
option, which means by default it would be 'kr_c'. Do you
recommend using 'ansi_c' as an option. What would be the
implication ? (Some other people are actually using the Pro*C).
By the way, Oracle has come back with the message that -
- this is bug 409906 & no patch available as of 24th Feb.
- the workaround is to use "define=_POSIX_4SOURCE" while doing
the pre-compilation.
This seems to do the trick, but I understand from the guys
actually using it that this has other implications on the C
code used.
So, in the meantime we wait for a patch from Oracle. Any other
suggestions please ?
Nandan
|