From: Elena Zannoni <ezannoni@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Andrew Cagney <ac131313@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: GDB CVS won't build on OSF4.0's cc
Date: Wed, 20 Mar 2002 07:08:00 -0000 [thread overview]
Message-ID: <15512.42422.404336.174227@localhost.redhat.com> (raw)
In-Reply-To: <orhenbhf3o.fsf@free.redhat.lsd.ic.unicamp.br>
Alexandre Oliva writes:
> On Mar 20, 2002, Elena Zannoni <ezannoni@redhat.com> wrote:
>
> > Andrew Cagney writes:
>
> >> > Other than the one that came with the patch posted to this mailing
> >> > list? I don't think so? Should I create one, install the patch and
> >> > then close it?
> >>
> >> I counted 4 or 5! You should look at gdb/390, there may still be
> >> ``issues''.
>
> > There is also 294 (which is essentially a duplicate of 390). Alex,
> > can you take a look? Maybe your configury test needs to be made a bit
> > more sophisticated.
>
> This is a totally different subject. This patch is for a build error
> on OSF1/DU/Tru64. Both PRs you mention are about TOC problems on
> AIX.
Sorry! Both Andrew and I were thinking of this other thread:
http://sources.redhat.com/ml/gdb/2002-02/msg00059.html
>
> >> > I'm not aware of such GDB policies :-(
>
> >> I think people doing this are viewed in a positive light (however there
> >> isn't any strict requirement :-).
>
> I never thought such a simple patch would take so long to get in (my
> fault; I dropped the ball in revising the patch as requested for a
> long while). Anyway, when a patch is ready, I see little value in
> creating a PR. To me, it feels like pure overhead. If you have a
> different opinion, please enlighten me :-)
>
Are any of the priority==high bugs related to this (as opposed to the
minimal-toc) problem?
Elena
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-03-20 15:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 3:20 Alexandre Oliva
2001-05-29 3:42 ` Alexandre Oliva
2001-05-29 4:12 ` Alexandre Oliva
2002-03-06 16:12 ` Alexandre Oliva
2002-03-06 17:58 ` Andrew Cagney
2002-03-06 18:52 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-25 8:43 ` Alexandre Oliva
2001-06-06 13:20 ` Elena Zannoni
2001-06-09 16:14 ` Alexandre Oliva
[not found] ` <Pine.SUN.3.91.1010610111224.5638I-100000@is>
2001-06-10 14:25 ` Alexandre Oliva
2001-06-11 1:06 ` Eli Zaretskii
2001-06-11 1:33 ` Russ Allbery
2001-06-11 7:04 ` Andrew Cagney
2001-06-11 6:32 ` Elena Zannoni
2001-06-11 6:34 ` Elena Zannoni
2002-03-06 16:36 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-19 9:41 ` Elena Zannoni
2002-03-19 10:31 ` Alexandre Oliva
2002-03-19 10:48 ` Elena Zannoni
2002-03-19 18:23 ` Alexandre Oliva
2002-03-19 18:39 ` Andrew Cagney
2002-03-19 20:40 ` Elena Zannoni
2002-03-20 0:00 ` Alexandre Oliva
2002-03-20 7:08 ` Elena Zannoni [this message]
2002-03-19 23:43 ` Alexandre Oliva
2002-03-20 7:10 ` Elena Zannoni
2002-03-20 14:27 ` Alexandre Oliva
2002-03-25 8:49 ` Alexandre Oliva
2001-05-29 9:30 ` Kevin Buettner
2001-05-30 19:54 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15512.42422.404336.174227@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox