From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5bb503f000534117,start
X-Google-Attributes: gid103376,public
From: "Richard A. Maffei" <rickal@visi.net>
Subject: ObjectAda 7.1, HP-UX 10.20, Oracle 7.X, and Intersolv's ODBC drivers
Date: 1998/07/09
Message-ID: <35A53688.61AEED29@visi.net>#1/1
X-Deja-AN: 369993748
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Reply-To: rickal@visi.net
NNTP-Posting-Date: Thu, 09 Jul 1998 17:53:21 EST
Newsgroups: comp.lang.ada
Date: 1998-07-09T00:00:00+00:00
List-Id: <comp.lang.ada>

Dear Ada-nauts,

In our attempt to switch our application from using Oracle's Pro*Ada to
ODBC, we have come across a stumbling block.  Namely, linking our Ada95
software to Intersolv's ODBC drivers through Aonix's ODBC bindings.

The problem arises when executing the program (everything compiles and
links fine).  The ODBC drivers implement shared libraries and when we
run the executable, we receive "unrecognizable symbol __shlinit"
errors.

With the assistance of Aonix and Intersolv, we confirmed which
libraries are to be included in the link command, but the errors still
arise.  Delving deeper into the problem, I found an article in HP's
support center stating that the system linker (ld) cannot handle C++
libraries (in which Intersolv's drivers are written).  To link in C++
libraries, HP's aCC compiler/linker is required.  However, the article
further states that when using the aCC compiler, the main procedure
needs to be written in C++ (shudder).

My questions are simple:  Has anyone successfully integrated an Ada95
application with Aonix's ODBC bindings and Intersolv's drivers on an
HP-UX 10.20 system?  If so (and I truly hope so), can anyone provide
some pointers into the process?  Or are there other alternatives to
what we are attempting?  Note that we require dynamic SQL capabilities.

Any assistance would be greatly appreciated.

v/r,
Rick Maffei