topic Re: Pro*C Compilation/Linking Problem in Operating System - HP-UX

Pro*C Compilation/Linking Problem

A Y Krishna — Wed, 12 Jan 2005 23:52:34 GMT

I have precompiled a Pro*c program (abc.pc) like this

node1> proc abc.pc

there were no errors

then I compiled it like

node1> cc abc.c

then I get the following error

Id: Unsatisfied Symbol "sqlcxt" in file abc.o
1 errors.

I am new to this, can anyone please help.

Thanks.

Re: Pro*C Compilation/Linking Problem

Sanjay Kumar Suri — Wed, 12 Jan 2005 23:58:45 GMT

Check this links:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=64515

http://www.orafaq.net/usenet/comp.databases.oracle.server/2000/06/13/0009.htm

sks

Re: Pro*C Compilation/Linking Problem

A Y Krishna — Thu, 13 Jan 2005 01:13:12 GMT

Thanks Sanjay.

But it didn't helped me (I think due to my limited knowledge). Problem is I am not having any makefile supplied by Oracle !! I don't find the demo directory too !!

I am using Oracle 10g on HP UX 11i.

Re: Pro*C Compilation/Linking Problem

Indira Aramandla — Thu, 13 Jan 2005 01:24:10 GMT

Hi krishan,

According to Oracle supported proc compilers one has to use:

HP ANSI C B.11.11.08+ & HP aC++ A.03.50+
HP92453-01 A.11.01.21 HP C (Bundled) Compiler
HP aC++ B3910B A.03.37
HP aC++ B3910B A.03.30 Language Support Library

Error â HP-UX Oracle10g ld Unsatisfied symbolâ may be solved by installing a certified compiler.

It is recommended to use the Oracle provided make file demo_proc.mk to compile/ link your programs. The make file is shipped in $ORACLE_HOME/precomp/demo/proc directory and can be used as follows.

make -f demo_proc.mk build EXE=program_name OBJS=program_name.o

example : If test.pc is the program name, then the make file can be used as :

make -f demo_proc.mk build EXE=test OBJS=test.o

If you have multiple modules accociated with your Pro*c application, then the make file can be used as :

make -f demo_proc.mk build EXE=application_name OBJS="mod1.o mod2.o mod3.o

So you may have to purshase a lisence for the new compiler and test to see if the problem is solved.

Indi

Re: Pro*C Compilation/Linking Problem

A Y Krishna — Thu, 13 Jan 2005 01:52:27 GMT

Thanks Indira.

I don't know which compiler is bundled with this. So, you see it as license problem !! OK, I will check this out.

Coming to the makefile, thanks again for your explanation. In my server I don't see a demo directory !!

I see two makefiles, /u01/oracle/precomp/lib/ins_precomp.mk and
/u01/oracle/precomp/lib/env_precomp.mk
are these of any help?

Apart from license can there be any other turnaround :(

Re: Pro*C Compilation/Linking Problem

Indira Aramandla — Thu, 13 Jan 2005 02:12:45 GMT

Hi Krishna,

You will require to add demo_proc.mk to an existing 0g installation to enable some Pro*C compilations.

There is a companion CD along with the 10G database. The component for the PRO*C compilers is there in that CD. Install from it.

Indira A

Re: Pro*C Compilation/Linking Problem

A Y Krishna — Thu, 13 Jan 2005 02:20:13 GMT

WOW !! this sounds promising. I will come back after installing that.

Thanks.

Re: Pro*C Compilation/Linking Problem

Yogeeraj_1 — Thu, 13 Jan 2005 02:26:02 GMT

hi,

after doing what Indira has suggested above, you may try to included the following sample makefile in the precompiler directory and use the symbolic in there to link with:

e.g.
=============================================
$(TARGET): $(SOURCE) $(SOURCE:.pc=.c) $(SOURCE:.pc=.o)
$(CC) $(LDFLAGS) -t -o $(TARGET) \
$(SOURCE:.pc=.o) -L$(ORACLE_HOME)/lib $(PROLDLIBS)

include $(ORACLE_PROC_MAKEFILE)

PROCFLAGS= ireclen=255 lines=yes $(PROC_ENV_FLAGS) \
include=$(ORACLE_HOME)/proc/lib
PROFLAGS=$(PROCFLAGS)

CFLAGS=-I. -g $(CC_ENV_FLAGS)
=============================================
where:
TARGET = name of program you want to create
SOURCE = list of .pc files you need to precompile/compile
PROC_ENV_FLAGS = any settings you want to override at make time for ProC
CC_ENV_FLAGS = any setting you want to override at make time for CC

then,
you should:
export ORACLE_PROC_MAKEFILE=$ORACLE_HOME/precomp/demo/proc/demo_proc.mk

hope this helps too!

regards
yogeeraj

Re: Pro*C Compilation/Linking Problem

A Y Krishna — Sat, 15 Jan 2005 01:44:17 GMT

finally I could do it.

the sqlcxt symbol is found in libsqlplus.a, i have included this file in the linker path as

cc abc.c -L $ORACLE_HOME/lib32 -l sqlplus

Once again, thanks everyone.

Re: Pro*C Compilation/Linking Problem

RaviKumar_8 — Mon, 12 Dec 2005 06:15:57 GMT

Hi,
This is RaviKumar.We are using the same OS environment(HP-UX 11i and Oracle 10g)I have faced the same problem.In our Oracle Server there is no demo_proc.mk.If u don't mind can u please send this file if u have
please contact the following mail ID.

ravi_mca80@yahoo.co.in
keyurg@gmail.com

If u send this it will be helpful for us.

Thanks,
Best Regards,
RaviKumar.T

Re: Pro*C Compilation/Linking Problem

scott ruffner_2 — Tue, 20 Dec 2005 16:12:09 GMT

I have oracle 10g running on a win2k sever but I need the files in the demo\proc\ directory from oracle 10g. I downloaded the companion cd and install but no demo_proc.mk can you email me them?

thanks,
scott

Re: Pro*C Compilation/Linking Problem

Vaibhav Patil — Fri, 16 Mar 2007 01:01:48 GMT

Hello ..

The file that contains sqlcxt is libclntsh.a, which is located under $(ORACLE_HOME)/lib32(probably for 32 bit mode) and under $(ORACLE_HOME)/lib(probably for 64 bit mode).

Try including that file explicitly in the .mk file. This may solve the problem.

In my case, the .pc file was compiling fine. But when i was trying to link it with another .c file, it was giving error "Undefined Symbol: .sqlcxt". It was finally resolved by explicitly adding an entry for the file $(ORACLE_HOME)/lib32/libclntsh.a in my .mk file for the .c file.