This is the mail archive of the
mailing list for the GCC project.
Re: dejagnu version update?
- From: Ramana Radhakrishnan <ramana dot gcc at googlemail dot com>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: Ramana Radhakrishnan <ramana dot radhakrishnan at foss dot arm dot com>, Andreas Schwab <schwab at suse dot de>, Jeff Law <law at redhat dot com>, Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>, David Malcolm <dmalcolm at redhat dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 17 Sep 2015 01:05:03 +0530
- Subject: Re: dejagnu version update?
- Authentication-results: sourceware.org; auth=none
- References: <1441916913-11547-1-git-send-email-dmalcolm at redhat dot com> <1441916913-11547-3-git-send-email-dmalcolm at redhat dot com> <55F720E6 dot 7020709 at redhat dot com> <4CB1399A-23A6-44F7-A25F-ECBD953E03A0 at gmail dot com> <55F74C3D dot 50504 at redhat dot com> <F5F4A096-2DD7-4635-9CB2-5A611247D71F at comcast dot net> <1B14D92A-0476-416B-A80D-A3083383C48D at gmail dot com> <55F879CB dot 2090607 at redhat dot com> <16565ACE-A56C-4971-BEA9-B299C9B40346 at comcast dot net> <mvmfv2eesa5 dot fsf at hawking dot suse dot de> <2BAFA587-8192-495C-B98C-BDA442B1A8A6 at comcast dot net> <55F997E3 dot 7030508 at foss dot arm dot com> <76A129A1-BF21-44BA-BC8C-09CC2E72AED1 at comcast dot net>
On Wed, Sep 16, 2015 at 11:27 PM, Mike Stump <email@example.com> wrote:
> On Sep 16, 2015, at 9:25 AM, Ramana Radhakrishnan <firstname.lastname@example.org> wrote:
>> Sorry about the obvious (possibly dumb) question.
>> Can't we just import a copy of dejagnu each year and install it as part of the source tree?
> TL;DR: No.
Thanks for the refresher on dll hell ;) My original inspiration for
thinking about the import just as I was leaving for the day was the
whole raft of target libraries we now build with gcc that are imported
(for convenience, coupling with compiler features etc. etc. ), why
not do the same with what is essentially required for any developer ?
I also see that the coupling for dejagnu is probably best left to
packaging systems - however we have a situations where developers face
version skew for dejagnu with the systems they are forced to develop
and test on. The question was really whether we as a community thought
that this cost with dejagnu was worth it and for someone to ask that
I am happy to settle for dealing with dejagnu the same way as other
prerequisites like gmp, mpfr / mpc i.e. put out a hard error when
testing if the right version of dejagnu is not found. For bonus points
update download_prerequisites to get the right version in the source
tree for people using older distributions and not being in a position
to upgrade their packages.