| Summary: | Build issue: tdemultimedia: Kaudiocreator won't build unless configure finds the cdda headers | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | tdemultimedia | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Darrell
2012-01-12 11:43:18 CST
This is a build issue and the bug report should be bumped to Blocker. The package builds with work-arounds. Bumping to Critical. Can you please be more specific? Where is the failure (configure or make)? Which header files exactly are affected? Hmm. I had to think about this. Been a while.... The package will build kaudiocreator only with extra-includes: --with-extra-includes=/usr/include/cdda: If the cdda with-extra-includes is missing then kaudiocreator will not build. The configure log will even say this: checking for cdparanoia... /usr/bin/cdparanoia checking cdda_interface.h usability... no checking cdda_interface.h presence... no checking for cdda_interface.h... no ... checking if kaudiocreator should be compiled... no Add --with-extra-includes=/usr/include/cdda: checking for cdparanoia... /usr/bin/cdparanoia checking cdda_interface.h usability... yes checking cdda_interface.h presence... yes checking for cdda_interface.h... yes ... checking if kaudiocreator should be compiled... yes Seems to me that --with-extra-includes should be used only when people install headers in non-standard locations. Seems the configure process should find all the header files listed above. Many other header files are in sub directories of /usr/include and with most packages, configure finds those. But I've lost count in the last few hours how many times I have been wrong today. :-) The cdda include subdirectory has been added in GIT hash 163e622. Please close this bug report if the issue is confirmed as fixed on your end. Thanks! Latest patch proved successful. The --with-extra-includes option no longer is needed. Resolved. Thank you! |