On Wed, Aug 08, 2018 at 01:17:49PM +0200, Bernhard Reutner-Fischer wrote: > On 7 August 2018 18:34:30 CEST, Segher Boessenkool > <seg...@kernel.crashing.org> wrote: > >On Mon, Aug 06, 2018 at 08:25:49AM -0700, Mike Stump wrote: > >> Since g++ already requires 1.5.3, it make no sense to bump to > >anything older that 1.5.3, so let's bump to 1.5.3. Those packaging > >systems and OSes that wanted to update by now, have had their chance to > >update. Those that punt until we bump the requirement, well, they will > >now have to bump. :-) > > > >"g++ requires it"? In what way? I haven't seen any issues with older > >dejagnu versions. > > I think > http://git.savannah.gnu.org/gitweb/?p=dejagnu.git;a=commit;h=5256bd82343000c76bc0e48139003f90b6184347
Ugh. If there is a conflict between the test-specific options and the testsuite run options, sometimes you should pick one, sometimes the other, and often skipping the test is best. Older dejagnu picked the run options, and now newer dejagnu picks the test-specific options, so now we cannot rely on *either* behaviour. At least for many years to come: we share most testcases with older GCC versions, which do not require dejagnu 1.5.3! What a mess. Segher
