Package links-2.25-r1 (but possibly present in earlier versions) compiled with USE="X freetype" (other flags irrelevant for this issue) doesn't give the user option to change default fonts (select external fonts) via item "Fonts" in "Setup" menu. However, manually extracting source and building with "./configure --enable-graphics && make" (no additional packages installed or removed) generates executable file where the aforementioned "Fonts" item is shown under "Setup" menu and selecting external fonts work as intended. The issue is probably in the ebuild file - most likely some error when translating USE flag "freetype" to appropriate ./configure flags. Reproducible: always Steps to reproduce: as above Expected results: menuitem "Setup->Fonts" shown when emerged with USE="freetype" and graphics support (X or fbcon)
I'm not able to see any difference between manual make and emerge, neither one has a Fonts menu. But I think this failed test in configure output is to blame: checking for ft2build.h... no I'm able to get the Fonts menu to show up if I manually inject "-I /usr/include/freetype2" into CFLAGS.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=43964fb5582198d01faf181e7a814cd38c7324d3 commit 43964fb5582198d01faf181e7a814cd38c7324d3 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2021-11-22 17:36:57 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2021-11-22 17:37:31 +0000 www-client/links: add include path for freetype Bug: https://bugs.gentoo.org/825318 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Ben Kohler <bkohler@gentoo.org> www-client/links/links-2.25-r2.ebuild | 173 ++++++++++++++++++++++++++++++++++ 1 file changed, 173 insertions(+)
Can you try 2.25-r2 and see if it works for you?
Created attachment 755518 [details] Output from ./configure (from portage)
Created attachment 755522 [details] Output from ./configure (manual)
Created attachment 755526 [details] Output from emerge --info
It is still not working. I have attached outputs from ./configure so you can compare them. Also, my emerge --info is attached if needed.
Can you attach config.log from the manual attempt? Yours seems to be succeeding in using pkgconfig for freetype, where mine doesn't (and your emerge attempt doesn't).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1bdef5e895d8e04fad7e9c223d485d5cd185900 commit e1bdef5e895d8e04fad7e9c223d485d5cd185900 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2021-11-23 15:25:23 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2021-11-23 15:26:08 +0000 www-client/links: better fix for freetype issue Bug: https://bugs.gentoo.org/825318 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Ben Kohler <bkohler@gentoo.org> www-client/links/{links-2.25-r2.ebuild => links-2.25-r3.ebuild} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Try r3, I think I have found the root cause-- without setting PKG_CONFIG, the build doesn't use pkg-config, and thus doesn't supply the right cflags/ldflags.
Created attachment 755670 [details] config.log from manual configuration
(In reply to Ben Kohler from comment #10) > Try r3, I think I have found the root cause-- without setting PKG_CONFIG, > the build doesn't use pkg-config, and thus doesn't supply the right > cflags/ldflags. The issue is resolved with r3. As far as I am concerned, you can close this bug.
