Miguel Rentes
Miguel Rentes

Reputation: 1003

gcc compilation leaves numerous temp files

I'm using Red Hat Enterprise Linux 5.4 (it's the latest version) and using gcc 4.1.2 to compile my C project. I've noticed that after the compilation, I get numerous tp* files with 0 bytes each inside the sources folder. I'm using the following options in gcc:

gcc -c -ggdb -D__linux -D__ORACLE__ -Wall -I/home/ (more -I here) -o file1.o file1.c

This works fine with no erros nor warnings and inside the sources folder I get the final .o files, the source files .c and also numerous files named tp* (for instance tp2YaayN, tp3sYGrz, etc.) and these tp files all have 0 bytes.

I'm also using Oracle's 10g Pro*C/C++ precompiler in some files to embed SQL statements in .pc files and to create .c files which are then compiled by gcc (see What is an Oracle precompiler?).

So, is there a way of not having these tp files created? I'm not sure these files are created by Oracle's Pro*C/C++ precompiler or by gcc, has anyone had this problem before or knows how to solve it?

Best regards,

Miguel Rentes

Upvotes: 1

Views: 544

Answers (2)

drizzt
drizzt

Reputation: 766

gcc does not leave any temporary files after compilation. they are generated from makefile or the oracle precompiler

Upvotes: 0

Rob Wells
Rob Wells

Reputation: 37131

Have you tried using -pipe so gcc communicates via pipes rather than temp files?

Upvotes: 1

Related Questions