James <p...@gnu.org> writes: > David > > On 24/05/16 18:20, David Kastrup wrote: >> James Lowe <p...@gnu.org> writes: >> >>> No core file was generated, I also upped the ulimit to 1GB. >>> >>> So perhaps it isn't the type of 'assertion' or crash you thought it >>> was after all? >> Perhaps. Knut's problem, however, sounded like it. If you have >> different results from Knut, things are even muddier than I thought. >> > Just in case it isn't obvious :) > > Your checkin stuck in staging is because patchy-staging-merge cannot > complete the make doc so it won't push to staging, not because there > is necessarily anything wrong with your patch.
I'll run one of my own. It's a nuisance that our results differ. Wait: my patchy runs with --enable-checking instead of --disable-optimising because I have the following patch applied:
>From fe1e215b2780a201c8fa85cefe76e894cdfc4a66 Mon Sep 17 00:00:00 2001 From: David Kastrup <d...@gnu.org> Date: Tue, 19 May 2015 10:21:13 +0200 Subject: [PATCH] Replace --disable-optimising with the faster --enable-checking --- patches/compile_lilypond_test/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patches/compile_lilypond_test/__init__.py b/patches/compile_lilypond_test/__init__.py index 22b2ff9..4a554f3 100644 --- a/patches/compile_lilypond_test/__init__.py +++ b/patches/compile_lilypond_test/__init__.py @@ -296,7 +296,7 @@ class AutoCompile (object): run ("find %s ! -wholename \"*out-test-baseline*\" -type f -exec rm -f {} \\;" % self.build_dir, wrapped=True) self.runner (self.build_dir, - os.path.join (self.src_build_dir, "configure") + " --disable-optimising", + os.path.join (self.src_build_dir, "configure") + " --enable-checking", issue_id, "configure", env=dict (config.items ("configure_environment"))) def patch (self, patch_issue, issue_id): -- 2.7.4
That was the long-term idea for creating --enable-checking in the first place. I just haven't put everybody on the same footing here. I'll revert this patch at my end and see whether I get anywhere different. Knut, did you use any options to ./configure ? config.log should mention how configure was called. -- David Kastrup
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel