From: Al Stone <ahs3@fc.hp.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Andrew Cagney <cagney@gnu.org>,
gdb@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: GDB 6.1 branch open
Date: Sat, 06 Mar 2004 00:10:00 -0000 [thread overview]
Message-ID: <1078531820.1048.22.camel@fcboson.fc.hp.com> (raw)
Message-ID: <20040306001000.eVn_unTvB2UtWI5tw45U-oldky_bCG9HXQXb2uSSQeo@z> (raw)
In-Reply-To: <20040302015123.GT1051@gnat.com>
More FYI: I now have nightly builds running for
both the mainline branch and the 6.1 branch for
- ia64-unknown-linux-gnu
I'm working on getting the testsuite to run
automagically, too.
Is there someplace we should email results? Perhaps
a binutils-testresults mailing list or something?
On Mon, 2004-03-01 at 18:51, Joel Brobecker wrote:
> > The GDB 6.1 branch has been created with the CVS tag:
> >
> > gdb_6_1-branch
>
> FYI: I have setup some nightly builds of this branch on the following
> platforms:
>
> - alpha-tru64 4.0f and 5.1a
> - pa-hpux 11.00
> - mips-irix 6.5
> - powerpc-aix 4.3.2 and 5.1
> - sparc-solaris 2.5 and 2.8
>
> It doesn't include running the testsuite automatically (we're sometimes
> having some problems with runaway processes), but at least we'll avoid
> the stupid build failure. And I'll make a point of running the testsuite
> manually on a regular basis.
--
Ciao,
al
----------------------------
Al Stone
Linux & Open Source Lab
Hewlett-Packard Company
E-mail: ahs3@fc.hp.com
----------------------------
next prev parent reply other threads:[~2004-03-06 0:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 23:02 Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Joel Brobecker
2004-03-02 1:51 ` Joel Brobecker
2004-03-19 0:09 ` Al Stone [this message]
2004-03-06 0:10 ` Al Stone
2004-03-19 0:09 ` Andrew Cagney
2004-03-09 1:11 ` 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=1078531820.1048.22.camel@fcboson.fc.hp.com \
--to=ahs3@fc.hp.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@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