cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/09/22/03:45:19

From: Christopher Croughton <crough45 AT amc DOT de>
Message-Id: <97Sep22.093941gmt+0100.11652@internet01.amc.de>
Subject: Re: Namespaces and g++
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Mon, 22 Sep 1997 08:44:19 +0100
Cc: crough45 AT amc DOT de, eldredge AT ap DOT net, djgpp AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.970921130845.9556E-100000@is> from "Eli Zaretskii" at Sep 21, 97 11:10:35 am
Mime-Version: 1.0

Eli Zaretskii wrote:
> 
> I think something's wrong with the way you sent your messages.  I use 
> gcc-bugs AT prep DOT ai DOT mit DOT edu without any problems.  What address did you use?

The one which GCC told me to use, not that one:

bug.cc:8: Internal compiler error.
bug.cc:8: Please submit a full bug report to `bug-g++@prep.ai.mit.edu'.

I'll try resubmitting it to gcc-bugs AT prep DOT ai DOT mit DOT edu and see if that
gets a better response - but the latest version of GCC should really
report the correct mailing list!  I fetched and compiled version 2.7.2.2
to check that the bug was still there, and that's what it reported...

(That was on DEC Alpha under OSF/1, but it also happened in DJGPP; since
DJGPP isn't officially supported by the GCC team I prefer to test it using
a platfor which they do support, so they can't come back and say "it was
your version at fault" - I don't know that they would, but in my experience
that's the first reaction of most software maintainers...)

Is gcc-bugs the mailing list?  Perhaps the other one just goes to a single
mailbox or something.

Chris C

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019