From:	broeker AT physik DOT rwth-aachen DOT de
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: the gcc -o option
Date:	22 Mar 2000 16:09:28 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	14
Message-ID:	<8bar7o$qm1$1@nets3.rz.RWTH-Aachen.DE>
References:	<38D8BB21 DOT 16397608 AT accord-soft DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 953741368 27329 137.226.32.75 (22 Mar 2000 16:09:28 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	22 Mar 2000 16:09:28 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Ghins Mathai <ghins AT accord-soft DOT com> wrote:
> The gcc -o option overwrites a file by default. Is there anyway by which
> I can prevent this ??

Not inside gcc. You can move/rename it aside, before starting gcc,
though.

OTOH: why would you want to do that? I find it hard to imagine a use
of gcc where I would *not* want to have its output file overwritten,
if it exists. I'm running gcc exactly _because_ that file needs to be
replaced by a newer one, usually.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -