Bug 92930

Summary: FTBFS, apparently due to incompatibiltiy with recent glibmm
Product: PulseAudio Reporter: Peter Mattern <pmattern>
Component: pavucontrolAssignee: pulseaudio-bugs
Status: RESOLVED FIXED QA Contact: pulseaudio-bugs
Severity: major    
Priority: medium CC: lennart, swojskichlopak
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: output make attempting to compile pavucontrol VCS

Description Peter Mattern 2015-11-12 22:22:43 UTC 
Created attachment 119610 [details]
output make attempting to compile pavucontrol VCS

Both pavucontrol 3.0 and latest VCS checkouts fail to build on up to date Arch Linux systems, apparently due to incompatibility with recent glibmm versions.

An output (which I can't judge in detail) of make attempting to compile pavucontrol from VCS is attached.

As it seemed to suggest that glibmm is involved I reverted the system to status of 2015-10-07 meaning among other a downgrade from glibmm 2.46.1 to 2.44.0.
On a system like this both pavucontrol versions stated above compiled and worked flawlessly. Same thing after upgrading glibmm to 2.45.2. Later versions of glibmm wouldn't compile any longer and I didn't perform further tests as these would have caused quite a lot of dependency problems.
Comment 1 Tanu Kaskinen 2015-11-12 23:20:02 UTC 
Did you reconfigure pavucontrol when you switched glibmm versions? I might have seen the same issues on my machine, which went away after I re-ran the configure script.
Comment 2 Peter Mattern 2015-11-12 23:42:23 UTC 
(In reply to Tanu Kaskinen from comment #1)

Any attempt to compile was made in a pristine source tree.
(Assuming that by "reconfigure" you mean reverting a particular source tree by running stuff like 'make clean' or the likes after former usage.)
Comment 3 Arun Raghavan 2015-11-13 04:11:51 UTC 
Looks like this is because glibmm 2.46 onwards needs C++11 support while building.
Comment 4 Tanu Kaskinen 2016-02-07 18:01:29 UTC 
*** Bug 94034 has been marked as a duplicate of this bug. ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.