Pro*C generating garbage files

[Warthog]

I recently installed 10gR2 on SuSE Linux 10.0.

My application uses Pro*C, but after re-installation, the proc command always generates three randomly named files beginning with tp.

For example, here's one of my compiler steps:

chris@dev[152]:~/src/dcsrv/DcsDB% ll tp*
ls: No match.

proc sqlcheck=full cpp_suffix=cxx code=cpp userid=magic/wizard char_map=string include=.. include=VC SharkQuoteTbl.pc oname=SharkQuoteTbl.cxx > SharkQuoteTbl.pc.L

chris@dev[154]:~/src/dcsrv/DcsDB% ll tp*
-rw------- 1 chris users 0 2006-12-07 20:21 tp0Eudr5
-rw------- 1 chris users 0 2006-12-07 20:21 tp25IiCs
-rw------- 1 chris users 0 2006-12-07 20:21 tpSxEK1L

They are zero-length, but really irritating - with 30 or so files to compile, this generates 90 of these files. Anyone have any ideas how to coax pro*c to stop generating these?

Anyone seen this problem before?

Thanks!
Warthog

[hrishy]

Hi

Can you please email me the pro C files maybe i can help.

my email id is hrishys at yahoo dot co dot uk

regards
Hrishy

[Warthog]

(oops, duplicate post deleted)

[Warthog]

It seems unrelated to the actual source being compiled. To prove it, I created a 0-length file "empty.pc" and did my normal compile step:

proc sqlcheck=full cpp_suffix=cpp code=cpp userid=magic/wizard char_map=string include=.. include=VC empty.pc oname=empty.cxx > empty.pc.L

And I still get the mysterious "tp" files.

I think I'm just going to resort to a cleanup script to delete all files named tp* which are 0-length, after each compile...