how to clean up files after unsuccessful "./configure"
 

hello all,
suppose someone is trying to install "gyach" or any othe software from source
obviously first step will be to untar...
now i would like to ask that if after untarring the source, when we do "./configure" inside the
directory of the software sometimes it doesn't work and throw errors..
but if that moment i type
i can see its files stored in some directories...
are not they overhead on the machine????
is it necessary to remove them...??
if yes then how..??? just deleting the directory containing that or what??

regards

generally

make clean

will clean those files
unless u have installed them or copied them on ur own to some other location


regards

i always wondered that too: does ./configure actually write anything anywhere, aside from a makefile or whatever? to my (non-programmer) way of thinking it always seemed like ./configure just kind of "looked over" your system to see what you had. i didn't know it wrote anything anywhere.


p.s. to the original poster: if you did the locate directly after the configure, it's unlikely that you are seeing new files. unless you did updatedb directly before doing locate, what's returned is what was already in the database.

Mr. masand wrote:
what if i've installed them to some other place..???
...
one more question..
won't "make clean" effect already compiled/installed programs in the system???

regards

yes ./configure only checks for the requirements of the package

i wanted to specify that there is a

make clean

command which can clear files generated if any,though they will not be generated by ./configure

regards