From: Jason Green <news AT jgreen4 DOT fsnet DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: problem
Date: Sat, 16 Dec 2000 21:18:01 +0000
Organization: Customer of Energis Squared
Lines: 47
Message-ID: <4vln3tsoqvuc1qrhqtf0u9ap5760pqv8a7@4ax.com>
References: <72 DOT 5e5e3fc DOT 276a0ca3 AT aol DOT com> <91disk$7oi$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
NNTP-Posting-Host: modem-94.colorado.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsg4.svr.pol.co.uk 977001494 27979 62.137.57.94 (16 Dec 2000 21:18:14 GMT)
NNTP-Posting-Date: 16 Dec 2000 21:18:14 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Newsreader: Forte Agent 1.7/32.534
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote:

> Tom10779 AT aol DOT com wrote:
> 
> > gxx -----.cpp -o -----.exe
> 
> Was *that* exactly your command line? Including '-----' as the
> filename base part? In that case, I think you may have hit a bug in
> gcc,

Indeed there does seem to be a bug in gcc:

$ gcc -v
Reading specs from d:/djgpp/lib/gcc-lib/djgpp/2.952/specs
gcc version 2.95.2 19991024 (release)
$ echo "int main(void){return 0;}" > foo.c
$ cp foo.c ./-.c
$ cp foo.c ./--.c
$ cp foo.c ./---.c
$ gcc foo.c
$ gcc ./-.c
$ gcc ./--.c
$ gcc ./---.c
$ gcc -.c
gcc.exe: unrecognized option `-.c'
gcc.exe: No input files
$ gcc --.c
gcc.exe: No input files
$ gcc ---.c
gcc.exe: No input files
$ gcc --
gcc.exe: Ambiguous abbreviation --
gcc.exe: No input files
$ gcc ---
gcc.exe: No input files
$ gcc -- foo.c
gcc.exe: Ambiguous abbreviation --
$ gcc --- foo.c
cc1.exe: Invalid option `-f-'
$

This does upset gxx too, although I couldn't recreate SIGABRT.

Maybe the OP chose those filenames to demonstrate the bug??  While not
a good choice of filename for real code, it is still workable. 

For example:  gxx ./-----.cpp -o ./-----.exe