This is the mail archive of the
mailing list for the GCC project.
Re: dejagnu version update?
- From: Martin Jambor <mjambor at suse dot cz>
- To: Trevor Saunders <tbsaunde at tbsaunde dot org>
- Cc: Jeff Law <law at redhat dot com>, Mike Stump <mikestump at comcast dot net>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Mon, 15 May 2017 17:54:06 +0200
- Subject: Re: dejagnu version update?
- Authentication-results: sourceware.org; auth=none
- References: <55F74C3D.firstname.lastname@example.org> <F5F4A096-2DD7-4635-9CB2-5A611247D71F@comcast.net> <1B14D92A-0476-416B-A80D-A3083383C48D@gmail.com> <55F879CB.email@example.com> <16565ACE-A56C-4971-BEA9-B299C9B40346@comcast.net> <firstname.lastname@example.org> <2BAFA587-8192-495C-B98C-BDA442B1A8A6@comcast.net> <55F997E3.email@example.com> <55F99A9F.firstname.lastname@example.org> <20150916172518.GB17834@tsaunders-iceball.corp.tor1.mozilla.com>
On Wed, Sep 16, 2015 at 01:25:18PM -0400, Trevor Saunders wrote:
> On Wed, Sep 16, 2015 at 10:36:47AM -0600, Jeff Law wrote:
> > I'd rather just move to 1.5 and get on with things. If some systems don't
> > have a new enough version, I'm comfortable telling developers on those
> > platforms that they need to update. It's not like every *user* needs
> > dejagnu, it's just for the testing side of things.
> yeah, it seems like a poor idea to slow down progress we make for all
> users to benefit a few people who want to develope on rather old
Could we at least make sure that machines in the FSF compile farm have
a new enough dejagnu before move to requiring at least 1.5?
I understand that may be a tall order, given that some machines
(e.g. gcc117) do not have dejagnu at all and this was reported some
time ago :-(