Bug 726561 - freetype-config breaks when only freetype-devel.i686 installed
Summary: freetype-config breaks when only freetype-devel.i686 installed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: freetype
Version: 15
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-29 02:01 UTC by Anna Wiggins
Modified: 2013-03-03 23:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-29 15:13:36 UTC
Type: ---


Attachments (Terms of Use)

Description Anna Wiggins 2011-07-29 02:01:26 UTC
Description of problem:

freetype-config doesn't return the correct include paths when freetype-devel.i686 is installed without freetype-devel.x86_64 being installed.


Version-Release number of selected component (if applicable):

freetype-devel.2.4.4-4.fc15


How reproducible:

At will


Steps to Reproduce:
1. Ensure that freetype-devel is not installed.
2. yum install freetype-devel.i686
3. freetype-config --cflags

  
Actual results:

output of command in step 3 is:

-I/freetype2 -I


Expected results:

output should be:

-I/usr/include/freetype2


Additional info:

Everything works fine once freetype-devel.x86_64 is also installed. So, on x86_64, I suppose freetype-devel.i686 should either work by itself, or pull the .x86_64 package in as a dependency.

Comment 1 Marek Kašík 2011-08-29 15:13:36 UTC
Hi Anna,

you just need to set $PKG_CONFIG_PATH variable appropriately (add "/usr/lib/pkgconfig/" there). freetype-config uses pkg-config internally which needs to know from where to get required data (these are in /usr/lib/pkgconfig/freetype2.pc for freetype-devel.i686). Since you are on x86_64 system, you need to specify that you want to use i686 version of the -devel package.
I'm closing this as notabug.

Regards

Marek


Note You need to log in before you can comment on or make changes to this bug.