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 789 - Build issue: kaffiene: does not detect header files in subdirectories
Summary: Build issue: kaffiene: does not detect header files in subdirectories
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Other
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-01-12 12:05 CST by Darrell
Modified: 2012-10-20 20:57 CDT (History)
2 users (show)

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

Attachments
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 Darrell 2012-01-12 12:05:26 CST 
The configure process does not look for subdirectories when searching for header files.

On Slackware the cdda headers are installed at /usr/include/cdda.

Installing header files into a subdirectory of /usr/include is common.

A workaround is to use the --with-extra-includes configure option, but the configure process should support subdirectories.
Comment 1 Darrell 2012-10-20 20:57:29 CDT 
Looks like this got fixed in commit d32030ae 2010-10-05, which updated kaffeine to the latest upstream version. The difference can be seen in kaffeine/kaffeine/configure.in.in between the 3.5.12 tarball sources and the commit date.

The commit date predates the bug report filing. Not sure what happened there. Likely I had --with-extra-includes in my build script for such a long time I stopped noticing. I was not using SVN at that time, only the 3.5.12 tarballs. The 3.5.13 tarballs did not exist until 2011-11-01. Two months later when I reported I was just then starting to learn to use GIT. At that point I must have rediscovered I had --with-extra-includes in the build script but did not validate whether the problem still existed.

That is the long way of saying doesn't matter --- the problem is long resolved.