Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!ncrlnk!rd1632!alr
From: alr@rd1632.Dayton.NCR.COM (alr)
Newsgroups: comp.databases
Subject: Re: Lisp to Oracle interface
Message-ID: <885@rd1632.Dayton.NCR.COM>
Date: 18 Jul 89 15:54:46 GMT
References: <59244@linus.UUCP>
Reply-To: alr@rd1632.UUCP ()
Organization: NCR Research & Development, Dayton, Ohio
Lines: 18

In article <59244@linus.UUCP> bds@mbunix (Smith) writes:
>We've been writing a Lisp to Oracle interface for a program we are
>developing on Suns running Lucid Common Lisp 3.0.  Since Oracle doesn't
>directly support Lisp, the needed functionality is written in C, and
>we use the Lucid to C foreign function call interface.
>
I've implemented the same kind of Lisp-Oracle system as a consultant for NCR.
I ran into the same _uname problem when I upgraded.
I fixed it by:
1.  calling (in my Makefile) the System V C compiler
/usr/5bin/cc   instead of the standard C compiler
2.  including "/usr/5lib/libc.a" in the list of foreign libraries
which I load into Lucid.

Mike Komichak
komichak@dayton.ncr.com
Liszt Programming, Inc.
(703) 683-3916 or (513) 445-1086