lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Staging/Master Merge - James' Patchy


From: David Kastrup
Subject: Re: Staging/Master Merge - James' Patchy
Date: Thu, 26 Apr 2012 13:57:33 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

address@hidden writes:

> Begin LilyPond compile, commit: bf2c7f09ff00e6c59877eff5ba5f880299ed95bf
>
>       Success:                ./autogen.sh --noconfigure
>
>       Success:                ../configure --disable-optimising
>
>       Success:                nice make clean -j7 CPU_COUNT=7
>
>       Success:                nice make -j7 CPU_COUNT=7
>
>       Success:                nice make test-baseline -j7 CPU_COUNT=7
>
> *** FAILED STEP ***
>
>       patch 
>
>       /home/james/patchy/issue6109058_1.diff
>
>       Success:                nice make test-clean -j7 CPU_COUNT=7
>
>       Success:                nice make clean
>
> *** FAILED STEP ***
>
>       patch --reverse
>
>       /home/james/patchy/issue6109058_1.diff
>
> Begin LilyPond compile, commit:       bf2c7f09ff00e6c59877eff5ba5f880299ed95bf

We really should get rid of that reverse patch nonsense.  Instead, nuke
the build directory and start from scratch.  Graham wanted to avoid that
because it would lose the test-baseline, but if one creates a
LILYPOND_BASELINES environment variable pointing to an outside
directory, make test-baseline will put a tarball there (and back again)
without the need to recompile anything.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]