David Kastrup writes:
> Thomas Klausner writes:
>
>>> Can you also report which of the preexisting files in lily/out/ gets
>>> overwritten by the problematic build, and which not?
>>
>> The header file is not recreated, but the cc file is:
>>
>> -rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
>> w
Thomas Klausner writes:
>> Can you also report which of the preexisting files in lily/out/ gets
>> overwritten by the problematic build, and which not?
>
> The header file is not recreated, but the cc file is:
>
> -rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
> work/lilypond-2.17.25/lily/out/pars
On 02/09/2013 4:33 AM, David Kastrup wrote:
Thomas Klausner writes:
Can you also report which of the preexisting files in lily/out/ gets
overwritten by the problematic build, and which not?
The header file is not recreated, but the cc file is:
But actually, this should not overwrite parse
Thomas Klausner writes:
>> Can you also report which of the preexisting files in lily/out/ gets
>> overwritten by the problematic build, and which not?
>
> The header file is not recreated, but the cc file is:
>
> -rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
> work/lilypond-2.17.25/lily/out/pars
> Can you also report which of the preexisting files in lily/out/ gets
> overwritten by the problematic build, and which not?
The header file is not recreated, but the cc file is:
-rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
work/lilypond-2.17.25/lily/out/parser.cc
-rw-r--r-- 1 pbulk buil
Thomas Klausner writes:
> I've followed the thread and can confirm that
> rm lily/out/parser.*
> before building lilypond fixes the problem for me.
Can you also report which of the preexisting files in lily/out/ gets
overwritten by the problematic build, and which not?
--
David Kastrup
I've followed the thread and can confirm that
rm lily/out/parser.*
before building lilypond fixes the problem for me.
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Thomas Klausner writes:
> I see you replied to my build issue in lilypond-2.17.24 that I should
> try a clean build.
>
> I've done that. I built versions 2.17.23, 2.17.24, and 2.17.25 from
> scratch in a sandbox, in different directories, and I still see this
> issue, in 2.17.24 and 2.17.25, but
Hi David!
I see you replied to my build issue in lilypond-2.17.24 that I should
try a clean build.
I've done that. I built versions 2.17.23, 2.17.24, and 2.17.25 from
scratch in a sandbox, in different directories, and I still see this
issue, in 2.17.24 and 2.17.25, but not in 2.17.23.
Also, I'v
