Path: utzoo!mnetor!uunet!husc6!mailrus!nrl-cmf!cmcl2!brl-adm!adm!mailer-daemon@lindy.stanford.edu From: mailer-daemon@lindy.stanford.edu (Mail Delivery Subsystem) Newsgroups: comp.unix.wizards Subject: Returned mail: User unknown Message-ID: <12682@brl-adm.ARPA> Date: 28 Mar 88 20:39:54 GMT Sender: news@brl-adm.ARPA Lines: 31 ----- Transcript of session follows ----- >>> RCPT To: <<< 550 ... Can't create output 550 //@UMUNHUM.STANFORD.EDU... User unknown ----- Unsent message follows ----- Received: by Forsythe.Stanford.EDU; Mon, 28 Mar 88 12:11:38 PST Received: by BYUADMIN (Mailer X1.25) id 1424; Mon, 28 Mar 88 13:11:43 MST Date: Sat, 26 Mar 88 11:49:52 PST Reply-To: Unix-Wizards@BRL.ARPA Sender: Unix-Wizards Mailing List From: Michael Chepponis Subject: Problems with GNU C 1.18 and GNU C++ 1.18.1 X-To: acornrc!bob@umunhum.stanford.edu X-Cc: unix-wizards@sem.brl.mil To: //@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@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.