Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 307823 - =kde-misc/filelight1.9_rc3 fails to build
Summary: =kde-misc/filelight1.9_rc3 fails to build
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-04 22:42 UTC by Philipp Reinkemeier
Modified: 2010-03-06 12:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Remove qimageblitz dependency (no-qimageblitz-dependency.patch,431 bytes, patch)
2010-03-04 22:47 UTC, Philipp Reinkemeier
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Reinkemeier 2010-03-04 22:42:38 UTC
When trying to emerge filelight compilation fails because of missing qimageblitz headers. This seems to be related to KDE 4.3 not depending on qimageblitz anymore, so this is NOT pulled in anymore by inheriting kde4-base in the ebuild.

Reproducible: Always

Steps to Reproduce:
1. emerge -Dav filelight
Actual Results:  
compiling fails with: "error: qimageblitz/qimageblitz.h: No such file or directory"

Expected Results:  
filelight compiles cleanly with no errors
Comment 1 Philipp Reinkemeier 2010-03-04 22:47:28 UTC
Created attachment 222121 [details, diff]
Remove qimageblitz dependency

Interestingly no feature of qimageblitz seems to be used actually. Its just an include, that is not needed. Applying the following patch and thereby simply removing the include-statement works for me. Filelight builds fine now and runs correct.
Comment 2 Samuli Suominen (RETIRED) gentoo-dev 2010-03-06 09:18:10 UTC
It's one-liner so I've added a sed for it in ebuild instead.

+  06 Mar 2010; Samuli Suominen <ssuominen@gentoo.org>
+  filelight-1.9_rc3.ebuild:
+  Remove unused qimageblitz include wrt #307823, thanks to Philipp
+  Reinkemeier for patch.

But if you don't want this problem to come back with next release, I suggest you mail the upstream author of filelight about it.
Comment 3 Philipp Reinkemeier 2010-03-06 12:42:07 UTC
Will do that.