Bug 131986 - Configure stops on cdparanoia if "--enable-new-ldflags" option is switched on
Summary: Configure stops on cdparanoia if "--enable-new-ldflags" option is switched on
Status: RESOLVED WORKSFORME
Alias: None
Product: kdemultimedia
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-07 08:22 UTC by Vladislav Mikhailikov
Modified: 2006-08-07 17:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladislav Mikhailikov 2006-08-07 08:22:27 UTC
Version:           3.5.4 (using KDE KDE 3.5.4)
Installed from:    Compiled From Sources
Compiler:          GNU GCC 4.1.1 Highly optimized, though all tests passed.
OS:                Linux

checking for snd_seq_create_simple_port in -lasound... yes
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 for cdrom_drive.cdda_device_name in cdda_interface.h... yes
checking for paranoia_init in -lcdda_paranoia... no
configure: error: --with-cdparanoia was given, but test for cdparanoia failed
error: Bad exit status from /usr/src/rpm/BUILD/rpm-tmp.30393 (%build)

------------------------------------------------------------------------------------
I found that problem was in option -Wl,--as-needed. I do suspect the outdated cdparanoia library and it's compilation and linking options. Disabling "--enable-new-ldflags" removes the error.
Comment 1 Rex Dieter 2006-08-07 17:24:16 UTC
This is most likely a bug in your build of cdparanoia (or your gcc toolchain).  If so, there's not much kdmm can (or should) do about it.

For the record, building kdmm using
--enable-new-ldflags --with-cdparanoia 
WORKSFORME using gcc-4.1.1 (Fedora Core 6,test1)

If you have additional evidence that this is indeed a kdemm issue, please re-open.