Summary: | media-libs/freetype-2.10.2-r1[harfbuzz,utils]: tttypes.h:27:10: error: #include expects "FILENAME" or <FILENAME> | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | i.Dark_Templar <idarktemplar> |
Component: | Current packages | Assignee: | Gentoo Fonts Team <fonts> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | bertrand, duncan, gentoo3, grknight, O01eg, paolo.pedroni, phils, vityokster, yamadharma |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
tttypes.h |
Description
i.Dark_Templar
2020-07-25 08:58:56 UTC
Created attachment 650696 [details]
build.log
Attaching full build log.
Here's the error:
In file included from /var/tmp/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/src/truetype/ttobjs.h:26,
from /var/tmp/portage/media-libs/freetype-2.10.2-r1/work/ft2demos-2.10.2/src/ttdebug.c:64:
/var/tmp/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/include/freetype/internal/tttypes.h:27:10: error: #include expects "FILENAME" or <FILENAME>
27 | #include FT_COLOR_H
| ^~~~~~~~~~
Please attach the file /var/tmp/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/include/freetype/internal/tttypes.h to this bug. Created attachment 650698 [details]
tttypes.h
Additionally, if I first emerge =media-libs/freetype-2.10.2-r1[harfbuzz,-utils] and then emerge =media-libs/freetype-2.10.2-r1[harfbuzz,utils], everything merges fine. I guess =media-libs/freetype-2.9.1-r3 doesn't have FT_COLOR_H defined, and while =media-libs/freetype-2.10.2-r1 has it defined in file "include/freetype/config/ftheader.h", during build system header is used instead of new version of header in build directory. # grep FT_COLOR_H -Ir /var/tmp/portage/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/include | grep define /var/tmp/portage/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/include/freetype/config/ftheader.h:#define FT_COLOR_H <freetype/ftcolor.h> Just a 'me too' comment; I'm having the same issue. Also encountering this problem. My full USE set: [X,adobe-cff,bzip2,cleartype_hinting,harfbuzz,infinality,png,utils] I also am able to confirm the workaround of merging the package twice, the first time with USE=-utils. I have the same bug. Portage 2.3.103 (python 3.7.8-final-0, default/linux/amd64/17.1/desktop, gcc-9.3.0, glibc-2.30-r8, 5.7.9-gentoo x86_64) ================================================================= System Settings ================================================================= System uname: Linux-5.7.9-gentoo-x86_64-Intel-R-_Core-TM-_i7-8750H_CPU_@_2.20GHz-with-gentoo-2.6 KiB Mem: 24470556 total, 17811180 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Sun, 26 Jul 2020 22:30:01 +0000 Head commit of repository gentoo: c267178e19fba9e88ff62e8d8981896875cb7cb5 sh bash 5.0_p17 ld GNU ld (Gentoo 2.33.1 p2) 2.33.1 app-shells/bash: 5.0_p17::gentoo dev-java/java-config: 2.3.1::gentoo dev-lang/perl: 5.30.3::gentoo dev-lang/python: 2.7.18-r1::gentoo, 3.7.8-r2::gentoo, 3.8.4-r1::gentoo dev-util/cmake: 3.16.5::gentoo sys-apps/baselayout: 2.6-r1::gentoo sys-apps/openrc: 0.42.1::gentoo sys-apps/sandbox: 2.18::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.11.6-r3::gentoo, 1.16.1-r1::gentoo sys-devel/binutils: 2.33.1-r1::gentoo sys-devel/gcc: 8.4.0-r1::gentoo, 9.3.0-r1::gentoo, 11.0.0_pre9999::gentoo sys-devel/gcc-config: 2.3.1::gentoo sys-devel/libtool: 2.4.6-r6::gentoo sys-devel/make: 4.2.1-r4::gentoo sys-kernel/linux-headers: 5.4-r1::gentoo (virtual/os-headers) sys-libs/glibc: 2.30-r8::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://rsync.gentoo.org/gentoo-portage priority: -1000 sync-rsync-verify-jobs: 1 sync-rsync-verify-max-age: 24 sync-rsync-extra-opts: sync-rsync-verify-metamanifest: yes (In reply to Phil Stracchino (Unix Ronin) from comment #7) > I also am able to confirm the workaround of merging the package twice, the > first time with USE=-utils. Ack. This workaround does work. I can confirm this workaround (USE=-utils) on x86. (In reply to i.Dark_Templar from comment #4) > Additionally, if I first emerge > =media-libs/freetype-2.10.2-r1[harfbuzz,-utils] and then emerge > =media-libs/freetype-2.10.2-r1[harfbuzz,utils], everything merges fine. > > I guess =media-libs/freetype-2.9.1-r3 doesn't have FT_COLOR_H defined, and > while =media-libs/freetype-2.10.2-r1 has it defined in file > "include/freetype/config/ftheader.h", during build system header is used > instead of new version of header in build directory. > > # grep FT_COLOR_H -Ir > /var/tmp/portage/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/ > include | grep define > /var/tmp/portage/portage/media-libs/freetype-2.10.2-r1/work/freetype-2.10.2/ > include/freetype/config/ftheader.h:#define FT_COLOR_H <freetype/ftcolor.h> It works for me. |