pat...@gnu.org writes: > 09:14:55 (UTC) Begin LilyPond compile, previous commit at > dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8 > 09:15:08 test-master-lock and PID entry exist but previous Patchy > run (PID 17333) died, resetting test-master-lock anyway. > 09:15:10 Merged staging, now at: dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8 > 09:15:11 Success: ./autogen.sh --noconfigure > 09:15:19 *** FAILED BUILD *** > /tmp/lilypond-autobuild/configure --disable-optimising > Previous good commit: a1467ba6de6240dda93009c907b05794ec9b8d54 > Current broken commit: dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8 > 09:15:19 *** FAILED STEP *** > merge from staging > Failed runner: /tmp/lilypond-autobuild/configure --disable-optimising > See the log file log-staging-configure.txt > 09:15:19 Traceback (most recent call last): > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 527, in handle_staging > self.configure (issue_id) > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 300, in configure > issue_id, "configure", env=dict (config.items ("configure_environment"))) > File > "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", > line 266, in runner > raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, > this_logfilename)) > FailedCommand: Failed runner: /tmp/lilypond-autobuild/configure > --disable-optimising > See the log file log-staging-configure.txt
Ugh, sorry for that. I need to tell my patchy to compile for 64bit or it will not get along with the libraries. Let's see whether I manage to do so. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel