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
