- **Patch**: push --> needs_work
- **Comment**:

Patch broke build, backed out of staging.

Error log excerpt:
10:35:17 (UTC) Begin LilyPond compile, previous commit at       
b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:20 Merged staging, now at:        b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:35:21        Success:                ./autogen.sh --noconfigure
10:35:34        Success:                /tmp/lilypond-autobuild/configure 
--enable-checking
10:35:37        Success:                nice make clean
10:37:17 *** FAILED BUILD ***
        nice make -j9 CPU_COUNT=9
        Previous good commit:   ce072002412d48f48cc4ff4620d82f700e816225
        Current broken commit:  b16c3d14f3d1f10aa919e70107e6103c67a9aa01
10:37:17 *** FAILED STEP ***
        merge from staging
        Failed runner: nice make -j9 CPU_COUNT=9
See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt
10:37:17 Traceback (most recent call last):
  File 
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 
528, in handle_staging
    self.build (issue_id=issue_id)
  File 
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", line 
316, in build
    issue_id)
  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: nice make -j9 CPU_COUNT=9
See the log file log-staging-nice-make--j9-CPU_COUNT=9.txt

Making lily/out/keyword.o < cc
Making lily/out/simple-spacer-scheme.o < cc
Making lily/out/episema-engraver.o < cc
Making lily/out/lyric-extender.o < cc
Making lily/out/includable-lexer.o < cc
Making lily/out/timing-translator.o < cc
Making lily/out/pango-font.o < cc
Making lily/out/part-combine-part-iterator.o < cc
Making lily/out/horizontal-bracket.o < cc
/tmp/lilypond-autobuild/lily/pango-font.cc: In member function
'Stencil Pango_font::pango_item_string_stencil(const PangoGlyphItem*)
const':
/tmp/lilypond-autobuild/lily/pango-font.cc:229:28: error: invalid use
of incomplete type 'PangoFcFont' {aka 'struct _PangoFcFont'}
  229 |   FcPattern *fcpat = fcfont->font_pattern;
      |                            ^~
In file included from /usr/include/pango-1.0/pango/pangoft2.h:29,
                 from /tmp/lilypond-autobuild/lily/pango-font.cc:20:
/usr/include/pango-1.0/pango/pangofc-font.h:47:16: note: forward declaration of 
'PangoFcFont' {aka 'struct _PangoFcFont'}
   47 | typedef struct _PangoFcFont      PangoFcFont;
      |                ^~~~~~~~~~~~
Making lily/out/clef-engraver.o < cc
Making lily/out/key-performer.o < cc
make[1]: ***
[/tmp/lilypond-autobuild/stepmake/stepmake/c++-rules.make:5:
out/pango-font.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: ***
[/tmp/lilypond-autobuild/stepmake/stepmake/generic-targets.make:6:
all] Error 2




---

** [issues:#5756] Make Pango >= 1.36 mandatory.**

**Status:** Started
**Created:** Thu Feb 13, 2020 12:54 PM UTC by Han-Wen Nienhuys
**Last Updated:** Tue Feb 18, 2020 05:36 AM UTC
**Owner:** Han-Wen Nienhuys


Pango 1.36 was released in 2013.

https://codereview.appspot.com/565660044


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to