It was to have all errors go to stderr (when launching LilyPond) for every platform when compiled with gub. I will no longer apply this patch.
On Jan 24, 2016 10:50 AM, "Richard Shann" <
address@hidden> wrote:
yes, that's the bit I've changed in print.c, you shouldn't need any
patch on this now (I'm not at all sure what your patch was doing
actually!)
Richard
On Sun, 2016-01-24 at 09:25 -0600, Jeremiah Benham wrote:
> It seems a patch I am applying fails to merge.
>
> http://denemo.org/~jjbenham/gub/target/mingw/log/denemo.log
>
> Here is the patch I was using:
>
> http://denemo.org/~jjbenham/gub/patches/denemo-1.1.4-run-lilypond.patch
>
> Jeremiah
>
> On Sat, 2016-01-23 at 14:48 -0600, Jeremiah Benham wrote:
> > It is 2.43. We should be good.
>
> It seems something *did* fail though:
> >
> [ ] denemo-mingw-0.0.0.zip 2016-01-24 00:53 8.4K
>
> Can you post the log?
>
> Richard
>
>
> > Jeremiah
> >
> > On Jan 23, 2016 11:35 AM, "Richard Shann" <address@hidden>
> > wrote:
> > Jeremiah,
> > I've just pushed some code that should fix the problem of
> > Windows not
> > knowing where LilyPond errors have occurred. It uses
> > g_spawn_check_exit_status() which is GLib 2.34 or later.
> From
> > what the
> > current libglib2.0.dll bundled with the zip file says it is
> > 2.43 but I
> > can't be sure it means that.
> > Can you let me know if it fails to compile?
> > Richard
> >
> >
>
>
>