From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: GDB 6.1 branch FROZEN
Date: Sat, 03 Apr 2004 16:06:00 -0000 [thread overview]
Message-ID: <406EDF67.2030201@gnu.org> (raw)
In-Reply-To: <20040403011932.93EC34B104@berman.michael-chastain.com>
> Andrew Cagney writes:
>
>>> My intention is to let the snapshot process churn something out
>>> "tonight", followed by a 6.1 candidate sometime "tomorrow".
>
>
> I'm publishing my next spin on i686-pc-linux-gnu about 30-40 hours
> from now. This includes gdb 6.0.91.
>
> I'll be sure to test the 6.1 candidate on hppa2.0w-hp-hpux11.11
> a few hours after it comes out. I can do something on i686-pc-linux-gnu
> as well.
>
> I just got word back from a user that 6.0.91 does not build
> on the user's hppa2.0w-hp-hpux11.00 system (pr gdb/1458).
What happens if --disable-nls is specified?
Andrew
next prev parent reply other threads:[~2004-04-03 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-03 1:19 Michael Elizabeth Chastain
2004-04-03 16:06 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 22:31 Andrew Cagney
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=406EDF67.2030201@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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