Re: Linking Oracle 7.3.2 applications

From: Jim Smith <jim_at_jimsmith.demon.co.uk>
Date: 1997/02/13
Message-ID: <kKstGHAuCsAzEwxb_at_jimsmith.demon.co.uk>#1/1


[Quoted] In article <5dpeec$evm_at_news.NL.net>, Michiel Schutler <michiel_at_enterprise.design.nl> writes
>Hi,
>
>I am using Oracle Server 7.3.2 and I would like to compile
>some freely available source packages, such as a module
>for Python.
>
>My problem is that most Makefiles are for Oracle 7.2 and as
>the library names changed for 7.3, these don't work anymore.A
>When I try to change a Makefile I end up with link lines like:
>
>gcc -shared -o oracle.so -s -O2 $(PYTHON_INC) oramodule.c osntab.o \
>$(ORACLE_LIB) -lsqlnet -lcommon -lncr -lcore3 -lnlsrtl3 -lcore3 -lclient \
>-lcommon -lnlsrtl3 -lepc -lgeneric -lnlsrtl3 -lsqlnet -lcore3 -lnlsrtl3 \
>-lcv6
>
>in which each library is repeated many times.
>
>Can anyone please tell me how to properly link an arbitrary program
>with Oracle 7.3?
>
Don't know about 7.3 but multiple library entries is pretty standard for oracle linking. It is down to a limitation in unix linkers where libraries are only scanned once. If libraries cross refer to each other then they need to appear more than once on the link line.

I notice you are using gcc. Oracle does not support gcc, although it can usually be made to work.

-- 
Jim Smith
Received on Thu Feb 13 1997 - 00:00:00 CET

Original text of this message