Created attachment 383500 [details] build.log Currently lilypond failes to compile on my system. The complete build.log and emerge.info will be attached. Here is the error message: open-type-font.cc: In function 'FT_Byte* load_table(const char*, FT_Face, FT_ULong*)': open-type-font.cc:39:71: error: 'FT_Load_Sfnt_Table' was not declared in this scope make[1]: *** [out/open-type-font.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/media-sound/lilypond-2.16.2/work/lilypond-2.16.2/lily' make: *** [all] Error 2 * ERROR: media-sound/lilypond-2.16.2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=media-sound/lilypond-2.16.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=media-sound/lilypond-2.16.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/media-sound/lilypond-2.16.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/lilypond-2.16.2/temp/environment'. * Working directory: '/var/tmp/portage/media-sound/lilypond-2.16.2/work/lilypond-2.16.2' * S: '/var/tmp/portage/media-sound/lilypond-2.16.2/work/lilypond-2.16.2' >>> Failed to emerge media-sound/lilypond-2.16.2, Log file: >>> '/var/tmp/portage/media-sound/lilypond-2.16.2/temp/build.log' * Messages for package media-sound/lilypond-2.16.2: * ERROR: media-sound/lilypond-2.16.2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=media-sound/lilypond-2.16.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=media-sound/lilypond-2.16.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/media-sound/lilypond-2.16.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-sound/lilypond-2.16.2/temp/environment'. * Working directory: '/var/tmp/portage/media-sound/lilypond-2.16.2/work/lilypond-2.16.2' * S: '/var/tmp/portage/media-sound/lilypond-2.16.2/work/lilypond-2.16.2'
Created attachment 383502 [details] emerge --info
I've just tried lilypond-2.18.2 and it compiles fine...
The trivial reason lies a few lines earlier: open-type-font.cc:26:31: warning: freetype/tttables.h: No such file or directory meaning this is a stable request.
*** Bug 522280 has been marked as a duplicate of this bug. ***
*** Bug 522390 has been marked as a duplicate of this bug. ***
Hi, why not merge something like this patch for lilypond-2.16.2 when using >=freetype-2.5.1? diff --git a/lily/freetype-error.cc b/lily/freetype-error.cc index 00e5cae..88af76c 100644 --- a/lily/freetype-error.cc +++ b/lily/freetype-error.cc @@ -31,7 +31,7 @@ const struct Freetype_error_message const char *err_msg; } ft_errors[] = -#include <freetype/fterrors.h> +#include FT_ERRORS_H ; diff --git a/lily/open-type-font.cc b/lily/open-type-font.cc index fc97b99..4d33d15 100644 --- a/lily/open-type-font.cc +++ b/lily/open-type-font.cc @@ -23,7 +23,7 @@ using namespace std; -#include <freetype/tttables.h> +#include FT_TRUETYPE_TABLES_H #include "dimensions.hh" #include "international.hh" diff --git a/lily/pango-font.cc b/lily/pango-font.cc index 70810b5..9057b9d 100644 --- a/lily/pango-font.cc +++ b/lily/pango-font.cc @@ -22,7 +22,7 @@ #define PANGO_ENABLE_BACKEND #include <pango/pangoft2.h> -#include <freetype/ftxf86.h> +#include FT_XFREE86_H #include <map> #include <cstdio> diff --git a/lily/ttf.cc b/lily/ttf.cc index be7cfe5..d84f0a3 100644 --- a/lily/ttf.cc +++ b/lily/ttf.cc @@ -20,7 +20,7 @@ #include <cstdio> #include "freetype.hh" -#include <freetype/tttables.h> +#include FT_TRUETYPE_TABLES_H #include "international.hh" #include "memory-stream.hh"
(In reply to Robert Spillner from comment #6) > why not merge something like this patch for lilypond-2.16.2 when using > >=freetype-2.5.1? It's past time to stabilize 2.18.2 so we should do that instead.
Alas, when's this going to happen? Why not patch this version so "emerge world" can run without interruption?
(In reply to Robert Spillner from comment #8) > Alas, when's this going to happen? Why not patch this version so "emerge > world" can run without interruption? Because patching will create a new ebuild revision which would generally go through the same stabilization process anyway. I'd advise adding 2.18.2 to your package.accept_keywords for now and wait for it to get stabilized.
2.18.2 is getting stabilized in bug #523818, this bug will be closed once it's stabilized.
2.18.2 is now stabilized.
