Re: regtests for previous stables failing

2017-10-30 Thread Thomas Morley
2017-10-29 8:44 GMT+01:00 Werner LEMBERG : >>> But I get >>> /home/hermann/lilypond-git/lily/pango-font.cc: In member function >>> 'Stencil Pango_font::pango_item_string_stencil(const PangoGlyphItem*) >>> const': >>> /home/hermann/lilypond-git/lily/pango-font.cc:166:55: error: >>> 'FT_Get_X11_Font_

Re: regtests for previous stables failing

2017-10-29 Thread Werner LEMBERG
>> But I get >> /home/hermann/lilypond-git/lily/pango-font.cc: In member function >> 'Stencil Pango_font::pango_item_string_stencil(const PangoGlyphItem*) >> const': >> /home/hermann/lilypond-git/lily/pango-font.cc:166:55: error: >> 'FT_Get_X11_Font_Format' was not declared in this scope >>bool

Re: regtests for previous stables failing

2017-10-28 Thread Thomas Morley
2017-10-28 19:06 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> 2017-10-28 18:27 GMT+02:00 David Kastrup : >>> Thomas Morley writes: >>> 2017-10-27 23:13 GMT+02:00 David Kastrup : > > It's a bit tricky. Maybe we should cherry-pick the necessary > compatibility patches to

Re: regtests for previous stables failing

2017-10-28 Thread David Kastrup
Thomas Morley writes: > 2017-10-28 18:27 GMT+02:00 David Kastrup : >> Thomas Morley writes: >> >>> 2017-10-27 23:13 GMT+02:00 David Kastrup : It's a bit tricky. Maybe we should cherry-pick the necessary compatibility patches to the stable branches' tips? If you want to bise

Re: regtests for previous stables failing

2017-10-28 Thread Thomas Morley
2017-10-28 18:27 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> 2017-10-27 23:13 GMT+02:00 David Kastrup : >>> >>> It's a bit tricky. Maybe we should cherry-pick the necessary >>> compatibility patches to the stable branches' tips? If you want to >>> bisect, you'd need to skim them in as

Re: regtests for previous stables failing

2017-10-28 Thread David Kastrup
Thomas Morley writes: > 2017-10-27 23:13 GMT+02:00 David Kastrup : >> >> It's a bit tricky. Maybe we should cherry-pick the necessary >> compatibility patches to the stable branches' tips? If you want to >> bisect, you'd need to skim them in as well, I guess. > > The compability patch is likely

Re: regtests for previous stables failing

2017-10-28 Thread Thomas Morley
2017-10-27 23:13 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> But in the light of David's last mail I revived my old LilyDev3 which has: >> $ make --version && gcc --version >> GNU Make 3.81 >> Copyright (C) 2006 Free Software Foundation, Inc. >> This is free software; see the source fo

Re: regtests for previous stables failing

2017-10-27 Thread Werner LEMBERG
>>> In that case, I can only think of our Makefiles not being >>> compatible with current make (there are also problems with current >>> g++ but you should not even have gotten as far had you encountered >>> those). > > Obviously David was right about the make-version. Do we need to fix > somethi

Re: regtests for previous stables failing

2017-10-27 Thread David Kastrup
Thomas Morley writes: > But in the light of David's last mail I revived my old LilyDev3 which has: > $ make --version && gcc --version > GNU Make 3.81 > Copyright (C) 2006 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. > There is NO warranty; not e

Re: regtests for previous stables failing

2017-10-27 Thread Thomas Morley
2017-10-27 17:06 GMT+02:00 James Lowe : > Hello > > On Fri, 27 Oct 2017 13:43:07 +0200, David Kastrup wrote: > >> Thomas Morley writes: >> >> > 2017-10-27 13:19 GMT+02:00 David Kastrup : >> > >> >> Maybe make check and/or test-baseline doesn't like a separate build >> >> directory? That's the on

Re: regtests for previous stables failing

2017-10-27 Thread James Lowe
Hello On Fri, 27 Oct 2017 13:43:07 +0200, David Kastrup wrote: > Thomas Morley writes: > > > 2017-10-27 13:19 GMT+02:00 David Kastrup : > > > >> Maybe make check and/or test-baseline doesn't like a separate build > >> directory? That's the only thing I can think of right now. > > > > Ok, will

Re: regtests for previous stables failing

2017-10-27 Thread David Kastrup
Thomas Morley writes: > 2017-10-27 13:19 GMT+02:00 David Kastrup : > >> Maybe make check and/or test-baseline doesn't like a separate build >> directory? That's the only thing I can think of right now. > > Ok, will try later, have to leave soon. > Though, I never experienced the problem with mor

Re: regtests for previous stables failing

2017-10-27 Thread Thomas Morley
2017-10-27 13:19 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> 2017-10-27 8:21 GMT+02:00 David Kastrup : >>> Thomas Morley writes: >>> 2017-10-26 23:26 GMT+02:00 David Kastrup : > make clean > > before calling autogen.sh . > > Possibly make distclean .

Re: regtests for previous stables failing

2017-10-27 Thread David Kastrup
Thomas Morley writes: > 2017-10-27 8:21 GMT+02:00 David Kastrup : >> Thomas Morley writes: >> >>> 2017-10-26 23:26 GMT+02:00 David Kastrup : >>> make clean before calling autogen.sh . Possibly make distclean . >>> >>> Being at lilypond-git/build (dev/2-18-test) I did: >>

Re: regtests for previous stables failing

2017-10-27 Thread Thomas Morley
2017-10-27 8:21 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> 2017-10-26 23:26 GMT+02:00 David Kastrup : >> >>> make clean >>> >>> before calling autogen.sh . >>> >>> Possibly make distclean . >> >> Being at lilypond-git/build (dev/2-18-test) I did: >> >> make clean >> make distclean >> c

Re: regtests for previous stables failing

2017-10-26 Thread David Kastrup
Thomas Morley writes: > 2017-10-26 23:26 GMT+02:00 David Kastrup : > >> make clean >> >> before calling autogen.sh . >> >> Possibly make distclean . > > Being at lilypond-git/build (dev/2-18-test) I did: > > make clean > make distclean > cd .. > rm -fr build > sh autogen.sh --noconfigure > mkdir

Re: regtests for previous stables failing

2017-10-26 Thread Thomas Morley
2017-10-26 23:26 GMT+02:00 David Kastrup : > Thomas Morley writes: > >> in order to research for >> https://sourceforge.net/p/testlilyissues/issues/5217/ >> I had the idea to look at regtest behaviour of previous stable lily-versions. >> >> Hence I checked out a stable-branch, added a regtest >> (

Re: regtests for previous stables failing

2017-10-26 Thread David Kastrup
Thomas Morley writes: > in order to research for > https://sourceforge.net/p/testlilyissues/issues/5217/ > I had the idea to look at regtest behaviour of previous stable lily-versions. > > Hence I checked out a stable-branch, added a regtest > (aaa-voiced-rest-dots.ly) did make, make test-baselin