[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: regtests for previous stables failing
From: |
Thomas Morley |
Subject: |
Re: regtests for previous stables failing |
Date: |
Fri, 27 Oct 2017 21:51:14 +0200 |
2017-10-27 17:06 GMT+02:00 James Lowe <address@hidden>:
> Hello
>
> On Fri, 27 Oct 2017 13:43:07 +0200, David Kastrup <address@hidden> wrote:
>
>> Thomas Morley <address@hidden> writes:
>>
>> > 2017-10-27 13:19 GMT+02:00 David Kastrup <address@hidden>:
>> >
>> >> 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 more up to date
>> > branches/master in a build-directory.
>>
>> Wait, patchy worked with a separate build.
>>
>> 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).
>
> address@hidden ~ $ make --version && gcc --version
> GNU Make 4.1
> Built for x86_64-pc-linux-gnu
> Copyright (C) 1988-2014 Free Software Foundation, Inc.
> Licence GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> gcc (Ubuntu 5.4.0-6ubuntu1~16.04.5) 5.4.0 20160609
> Copyright (C) 2015 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
For me exactly the same!
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 even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for i486-pc-linux-gnu
gcc (Debian 4.7.2-5) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
All worked there.
Obviously David was right about the make-version. Do we need to fix
something? At least with more current code all is working as well.
The results of the exercise at
https://sourceforge.net/p/testlilyissues/issues/5217/#ae0c/7c60/8bbe
ff
Thanks again,
Harm
- regtests for previous stables failing, Thomas Morley, 2017/10/26
- Re: regtests for previous stables failing, David Kastrup, 2017/10/26
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/26
- Re: regtests for previous stables failing, David Kastrup, 2017/10/27
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/27
- Re: regtests for previous stables failing, David Kastrup, 2017/10/27
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/27
- Re: regtests for previous stables failing, David Kastrup, 2017/10/27
- Re: regtests for previous stables failing, James Lowe, 2017/10/27
- Re: regtests for previous stables failing,
Thomas Morley <=
- Re: regtests for previous stables failing, David Kastrup, 2017/10/27
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/28
- Re: regtests for previous stables failing, David Kastrup, 2017/10/28
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/28
- Re: regtests for previous stables failing, David Kastrup, 2017/10/28
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/28
- Re: regtests for previous stables failing, Werner LEMBERG, 2017/10/29
- Re: regtests for previous stables failing, Thomas Morley, 2017/10/30
- Re: regtests for previous stables failing, Werner LEMBERG, 2017/10/27