From: Doug Evans <dje@google.com>
To: gdb <gdb@sourceware.org>, Pedro Alves <palves@redhat.com>
Subject: Re: Cleaning out obsolete bugs in bugzilla
Date: Wed, 12 Mar 2014 16:41:00 -0000 [thread overview]
Message-ID: <CADPb22RnA0aDsndyyoQu0gJ8spcWf1wr5taeqebFhUJK1ZLr0g@mail.gmail.com> (raw)
In-Reply-To: <CADPb22ROq5ieBxJKFpBxOFYx_wSn-FT4A6j5HG1XTVp-O3_n0w@mail.gmail.com>
Hi. I'll conclude from this that there is no disagreement with
closing such obsolete bugs as WONTFIX is ok.
I'll update the wiki accordingly.
ref: https://sourceware.org/ml/gdb/2014-02/msg00073.html
---------- Forwarded message ----------
From: palves at redhat dot com <sourceware-bugzilla@sourceware.org>
Date: Wed, Mar 12, 2014 at 3:10 AM
Subject: [Bug build/9101] Can not compile gdb-6.3 on AIX 5.2 with gcc 3.4.4
To: gdb-prs@sourceware.org
https://sourceware.org/bugzilla/show_bug.cgi?id=9101
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |palves at redhat dot com
Resolution|--- |WONTFIX
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
As this is within bfd/rs6000-core.c, it would really be a binutils bug. Given
6.3 is old and long gone out of support, and current mainline definitely builds
on AIX, I'm going to close this. I'm sorry nobody followed up on this when it
was filed...
next prev parent reply other threads:[~2014-03-12 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 17:58 Doug Evans
2014-03-12 16:41 ` Doug Evans [this message]
2014-03-12 16:59 ` Pedro Alves
2014-03-12 17:10 ` Doug Evans
2014-03-12 17:24 ` Pedro Alves
2014-03-31 17:42 ` Doug Evans
2014-03-12 17:15 ` Andreas Schwab
2014-03-12 17:22 ` Pedro Alves
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=CADPb22RnA0aDsndyyoQu0gJ8spcWf1wr5taeqebFhUJK1ZLr0g@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=palves@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