From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sources.redhat.com>
Subject: 5.1 Release criteria (with patch)
Date: Sat, 07 Jul 2001 10:35:00 -0000 [thread overview]
Message-ID: <3B47485E.9040100@cygnus.com> (raw)
Hello,
I've applied a knife to the 5.1 release criteria - there is one thing
left to do.
Among the things I've allowed to fall off (or not climb on) the back of
the cart:
o targets CRIS, s390, mips-linux
Here, I think all the generic problems
have been addressed so the remaining
patches should just drop in.
If they squeeze into 5.1 then cool if not
then oops
o sparc/linux
here to, to be honest, I'm not sure what the
status is. I do know the GNU/Linux/SPARC64
patches need more work.
Andrew
From chastain@cygnus.com Sat Jul 07 10:44:00 2001
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: 5.1 Release criteria (with patch)
Date: Sat, 07 Jul 2001 10:44:00 -0000
Message-id: <200107071645.JAA16457@bosch.cygnus.com>
X-SW-Source: 2001-07/msg00060.html
Content-length: 454
native hppa1.1-hp-hpux10.20 does not build. See PR gdb/63:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&databse=gdb&pr=63
"build failure, native hppa1.1-hp-hpux10.20, no_shared_libraries"
native hppa2.0w-hp-hpux11.00 probably also has this problem. Right now
it has an ltconfig problem standing in front so I can't see.
I don't know if "hpux gdb builds" merits a place in TODO or not,
that's the release manager's decision.
MichaelC
next reply other threads:[~2001-07-07 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 10:35 Andrew Cagney [this message]
2001-07-09 3:02 ` Orjan Friberg
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=3B47485E.9040100@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@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