Bug 115435 - Build fails because of freetype include errors
Summary: Build fails because of freetype include errors
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: qt
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-12 15:19 UTC by Enrico Scholz
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-02-12 17:00:47 UTC
Embargoed:


Attachments (Terms of Use)
fixes freetype include errors (443 bytes, patch)
2004-02-12 15:22 UTC, Enrico Scholz
no flags Details | Diff

Description Enrico Scholz 2004-02-12 15:19:16 UTC
Description of problem:

| $ rpm --rebuild qt-3.3.0-0.2.src.rpm
| ...
| red-mt/qclipboard_x11.o kernel/qclipboard_x11.cpp
| In file included from /usr/X11R6/include/X11/Xft/Xft.h:41,
|                  from kernel/qt_x11_p.h:152,
|                  from kernel/qtaddons_x11.cpp:25:
| /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!"
| /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files."
| /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
| /usr/include/freetype2/freetype/freetype.h:23:2: #error "  #include <ft2build.h>"
| /usr/include/freetype2/freetype/freetype.h:24:2: #error "  #include FT_FREETYPE_H"
| make[1]: *** [.obj/release-shared-mt/qtaddons_x11.o] Error 1


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

qt-3.3.0-0.2
freetype-2.1.7-1.bytecode


How reproducible:

100%

Comment 1 Enrico Scholz 2004-02-12 15:22:55 UTC
Created attachment 97613 [details]
fixes freetype include errors

Patch was created by following the suggestions

Comment 2 Than Ngo 2004-02-12 17:00:47 UTC
it's already fixed in qt-3.3.0, which will be available in rawhide soon.


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