By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1295 - Build issue: unnecessary and potentially harmful check in tdegraphics/kfile-plugins/dependencies/poppler-tqt/ConfigureChecks.cmake
Summary: Build issue: unnecessary and potentially harmful check in tdegraphics/kfile-p...
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdegraphics (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: All Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 1300
  Show dependency tree / graph
 
Reported: 2012-10-30 06:51 CDT by Alexander Golubev (Fat-Zer)
Modified: 2013-01-05 09:15 CST (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
a patch to fix the issue (695 bytes, patch)
2012-10-30 06:51 CDT, Alexander Golubev (Fat-Zer) 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Golubev (Fat-Zer) 2012-10-30 06:51:14 CDT 
Created attachment 942 [details]
a patch to fix the issue

See the patch.

btw. I've already posted several bugs associated with cmake files. All of them are quite small and I don't want to flood bugzilla with them. Maybe I'm supposed to create a single bug and post my patches/complaints there?
Comment 1 Darrell 2012-10-30 11:59:55 CDT 
Your choice. If the patches are very similar then consider one bug report. But separate reports is harmless too and avoids "losing" a patch in one report that gets cluttered.
Comment 2 Darrell 2012-10-31 14:04:07 CDT 
I'm updating the summary to "Build issue:" because that is what we have configured in our search links. :)
Comment 3 Darrell 2012-10-31 16:18:50 CDT 
I tested this patch only from the perspective of watching for problems when building the full package rather than trying to build separate component packages. No problems found during the build.

I have not looked for or tested any possible usability issues.

I would like Slavek or Tim to provide additional testing before pushing to GIT.
Comment 4 Slávek Banko 2013-01-05 09:15:08 CST 
Fixed in GIT hash 3fe3a36f