Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!shelby!lindy!liemandt
From: liemandt@lindy.Stanford.EDU (Joe Liemandt)
Newsgroups: comp.databases
Subject: Re: C appl. Oracle-Mac v1.0
Message-ID: <4846@lindy.Stanford.EDU>
Date: 20 Sep 89 22:42:27 GMT
References: <206600001@s.cs.uiuc.edu>
Sender: liemandt@lindy.Stanford.EDU (Joe Liemandt)
Reply-To: liemandt@lindy.Stanford.EDU (Joe Liemandt)
Organization: Stanford University
Lines: 21

In article <206600001@s.cs.uiuc.edu> detert@s.cs.uiuc.edu writes:
>
>I'm trying to write some simple C subroutines that access a database supported 
>by Oracle's RDBMS for the Macintosh, version 1.0, but can't get past the linking
>step : 
>  i precompile the source code (with Oracle's Pro*C) and compile (using MPW
>  version 3.0's C compiler) with no problem, but when i try to link (using MPW's
>  linker) my .o file with the necessary Oracle-supplied-executables, i get
>  'undefined entry' errors from 3 of the Oracle-supplied-executables. 
>

Your problem is simply that you are trying to access the MPW 2.0 libraries
which are supplied with ORACLE 1.0 from MPW 3.0. MPW's calling conventions
changed from 2.0 to 3.0, so calls to System Routines like Hlock and HUnlock
are now accessed with different capitalization and, I believe, some other, more
significant changes.  You need to either use MPW 2.0 and ORACLE 1.0,
or  MPW 3.0 and ORACLE 1.1. The upgrade to ORACLE supplies the
nescessary PRO*C objects in a number of different object library
formats, including MPW 3.0 and, I believe, THINK C. Some simple
programs that I could not link under ORACLE 1.0 linked and worked fine
with the new ORACLE.  The upgrade to 1.1 is $100-150, I think.