Re: GNATS: gdb-prs@ -> gdb@?

[Andrew Cagney <ac131313@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

> On Tue, Sep 24, 2002 at 06:51:30PM -0400, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> Anyone know something about GNATS?
>> 
>> I think I know why the ``send email to interested parties'' URL on the 
>> GDB's GNATS web page contains:
>> 
>> nobody@
>> The e-mail address of things like ``Responsible: unassigned'' get mapped 
>> onto nobody@ because they can't be mapped onto nothing (That gets 
>> remapped to unassigned@.  True?).  Same for a few others.  I think we 
>> can live with this one.
>> 
>> gdb-prs@
>> The contact address for the ``net'' and ``unknown'' customers is gdb-prs@!
>> 
>> What do people think of changing this?  For instance, just setting it to 
>> gdb@ or nobody@ (like most other things).
> 
> 
> nobody@ would be preferable to gdb@, I think...
> 
> 
>> I also don't remember the rationale behind gdb-gnats@ (where to send a 
>> bug report) vs gdb-prs@ (where the bug reports appear).  I suspect that 
>> it is to stop people accidently re-sending to gdb-gnats?
> 
> 
> Isn't gdb-gnats input into the gnats DB, and gdb-prs output from it?

I think its configured.

The attached shows up a second problem.  I can't reply to your reply as 
the headers put it down as being from gdb-prs.  Arrrg.

Andrew


[-- Attachment #2: mailbox-message://ac131313@movemail/fsf/gdb/prs#780100 --]
[-- Type: message/rfc822, Size: 3728 bytes --]

From: Daniel Jacobowitz <drow@mvista.com>
To: nobody@sources.redhat.com
Cc: gdb-prs@sources.redhat.com,
Subject: Re: gdb/722: Encounter "__builtin_va_alist undeclared" during building GDB
Date: 26 Sep 2002 01:58:01 -0000
Message-ID: <20020926015801.2088.qmail@sources.redhat.com>

The following reply was made to PR gdb/722; it has been noted by GNATS.

From: Daniel Jacobowitz <drow@mvista.com>
To: shoang@northropgrumman.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/722: Encounter "__builtin_va_alist undeclared" during building GDB
Date: Wed, 25 Sep 2002 21:52:00 -0400

 On Thu, Sep 26, 2002 at 01:45:54AM -0000, shoang@northropgrumman.com wrote:
 > 
 > >Number:         722
 > >Category:       gdb
 > >Synopsis:       Encounter "__builtin_va_alist undeclared" during building GDB
 > >Confidential:   no
 > >Severity:       critical
 > >Priority:       high
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Wed Sep 25 18:48:02 PDT 2002
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Sonny Hoang
 > >Release:        5.2.1
 > >Organization:
 > >Environment:
 > SUN 4u running Sun OS Release 5.7
 > >Description:
 > I download and extract files into directory gdb5.2.1 then I go into that directory running "./configure sun4" then I enter "make".  After a while of compiling, it gave me several errors in concat.c file saying:
 > 
 > function `concat_length':
 > `__builtin_va_alist' undeclared (first use in this function)
 > function `concat_copy':
 > `__builtin_va_alist' undeclared (first use in this function)
 > 
 > and etc.
 > 
 > I don't know what to do.  I need help please.
 
 Sun4 is SunOS 4.  Try using a solaris2 configuration triplet.  Try
 sparc-solaris2 maybe?
 
 -- 
 Daniel Jacobowitz
 MontaVista Software                         Debian GNU/Linux Developer