Returned mail: User unknown

Tue Mar 29 06:50:21 AEST 1988

   ----- Transcript of session follows -----
>>> RCPT To:<//+ at umunhum.stanford.edu>
<<< 550 <//+ at umunhum.stanford.edu>... Can't create output
550 //+ at UMUNHUM.STANFORD.EDU... User unknown

   ----- Unsent message follows -----
Received: by Forsythe.Stanford.EDU; Mon, 28 Mar 88 12:11:47 PST
Received: by BYUADMIN (Mailer X1.25) id 1425; Mon, 28 Mar 88 13:11:44 MST
Date:         Sat, 26 Mar 88 11:49:52 PST
Reply-To: Unix-Wizards at BRL.ARPA
Sender: Unix-Wizards Mailing List <UNIX-WIZ%NDSUVM1.BITNET at Forsythe.Stanford.EDU>
From: Michael Chepponis <cheppo at umunhum.stanford.edu>
Subject:      Problems with GNU C 1.18 and GNU C++ 1.18.1
X-To:         acornrc!bob at umunhum.stanford.edu
X-Cc:         unix-wizards at sem.brl.mil
To: "000," <//+ at UMUNHUM.STANFORD.EDU>
In-Reply-To:  Bob Weissman's message of 16 Mar 88 22:21:47 GMT

Supposedly every version of GNU C is tested for bootstrapping itself
on a microvax at MIT before it is distributed.  But that might be
a different version of Unix.

The most effective way to address your problems would be to
inform the people who would like to do something about them,
by sending a bug report.  Read the chapter on reporting bugs
in the Info file `internals' and send a bug report to
bug-gcc at prep.ai.mit.edu.

I'm not an expert on GNU C myself, which is why I suggest you
talk to the people who are.