pat...@gnu.org writes:
> 15:20:22 (UTC) Begin LilyPond compile, previous commit at
> 65aaa35a119053e92a608fbedceb20762787d21b
> 15:20:27 Merged staging, now at: 65aaa35a119053e92a608fbedceb20762787d21b
> 15:20:28 Success: ./autogen.sh --noconfigure
> 15:20:36 *** FAILED BUILD ***
> /tmp/lilypond-autobuild/configure --enable-checking
> Previous good commit: 8a493b7bc9aa4d34cd2970fc2223ec6920f0ed02
> Current broken commit: 65aaa35a119053e92a608fbedceb20762787d21b
> 15:20:36 *** FAILED STEP ***
> merge from staging
> Failed runner: /tmp/lilypond-autobuild/configure --enable-checking
> See the log file log-staging-configure.txt
> 15:20:36 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
> --enable-checking
> See the log file log-staging-configure.txt
Ugh. Forget this and the previous (but simultaneously sent from my mail
queue) mail. That's what happens when I configure (incompletely) back
and forth between amd64 architecture and i386 architecture in order to
check out code generation problems.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
