Red Hat Bugzilla – Bug 1368141
freetype-config --libtool prints path to non-existent libtool library file
Last modified: 2017-08-01 12:44:58 EDT
Description of problem: freetype-config --libtool prints pat to non-existent libtool library file Version-Release number of selected component (if applicable): freetype-config --version 16.0.10 freetype-config --ftversion 2.4.11 How reproducible: Always Steps to Reproduce: 1. execute freetype-config --libtool 2. file /usr/lib64/libfreetype.la 3. Actual results: /usr/lib64/libfreetype.la: cannot open (No such file or directory) Expected results: valid path to an existing file Additional info:
Since we don't ship static libraries using the flag should show empty string.
I've fixed this at Fedora rawhide, thank you for this report.
Still reproducible - there's no output (except an empty line) environment: cat /etc/redhat-release Red Hat Enterprise Linux Workstation release 7.4 Beta (Maipo) freetype-2.4.11-15.el7.x86_64 freetype-devel-2.4.11-15.el7.x86_64 freetype-debuginfo.x86_64 0:2.4.11-15.el7 freetype-demos.x86_64 0:2.4.11-15.el7
(In reply to Jiri Prajzner from comment #5) > Still reproducible - there's no output (except an empty line) That is correct and intentional. We don't ship the static library libfreetype.la.
Ah, sorry. I overlooked the comment #2. Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1965