Bug 678600 – media-sound/pulseeffects-4.4.7 - ../pulseeffects-4.4.7/src/spectrum_ui.cpp:26:26: error: cannot call member function ‘void SpectrumUi::init_custom_color()’ without object

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Manuel Garcia Wolff 2019-02-22 17:49:46 UTC]

Created attachment 566096 [details]
build.log

media-sound/pulseeffects-4.4.7 fails to build. I have attached the log files as indicated by the error message.

[Comment 1 Manuel Garcia Wolff 2019-02-22 17:50:18 UTC]

Created attachment 566098 [details]
emerge -pqv '=media-sound/pulseeffects-4.4.7::gentoo'

[Comment 2 Manuel Garcia Wolff 2019-02-22 17:51:03 UTC]

Created attachment 566100 [details]
emerge --info '=media-sound/pulseeffects-4.4.7::gentoo'

[Comment 3 Matthew Thode ( prometheanfire ) 2019-02-22 18:56:27 UTC]

I'm not sure which flag it is, but one of them probably needs to be statically enabled now.  Can you enable mda-lv2 (my best guess atm)?

-bs2b -calf -mda-lv2 -rubberband

[Comment 4 Manuel Garcia Wolff 2019-02-22 19:12:46 UTC]

Same error with the mda-lv2 USE flag. 

I also tried with all USE flags:

# USE="mda-lv2 bs2b calf rubberband" emerge pulseeffects

I got a similar error:

==
../pulseeffects-4.4.7/src/blacklist_settings_ui.cpp:55:38: error: cannot call member function ‘void BlacklistSettingsUi::populate_blacklist_in_listbox()’ without object
         populate_blacklist_in_listbox();
==

[Comment 5 Matthew Thode ( prometheanfire ) 2019-02-22 19:25:38 UTC]

I wonder if it's a gtk/cairo/pango/etc thing,.

[Comment 6 Manuel Garcia Wolff 2019-02-22 22:35:01 UTC]

I am using:

x11-libs/gtk+-3.24.1
x11-libs/cairo-1.16.0-r2
x11-libs/pango-1.42.4

These seem to be pretty recent versions. Should I try upgrading to the very latest versions of those three packages?

[Comment 7 Matthew Thode ( prometheanfire ) 2019-02-22 22:57:07 UTC]

I'm running stable on amd64 for it, so probably not.  Perhaps this should be an upstream bug.

[Comment 8 Manuel Garcia Wolff 2019-02-23 01:39:57 UTC]

OK, I will report this bug upstream.

[Comment 9 Manuel Garcia Wolff 2019-02-23 19:47:13 UTC]

I created an upstream bug[1]. There, wwmm recommended to try with a newer gcc version than the one I am using, which is 6.4.0. I switched to gcc-7.3.0 and that solved the problem.

[1] https://github.com/wwmm/pulseeffects/issues/444

[Comment 10 Matthew Thode ( prometheanfire ) 2019-02-23 19:49:57 UTC]

makes sense, I'll be bumping pulseeffects to 4.5.0 today probably and that'll include the gcc req (>=7.3.0).  I'm on 8.2.0-r6 right now (soon to be 8.3.0).

[Comment 11 Manuel Garcia Wolff 2019-02-23 19:51:45 UTC]

Cool, thanks.

[Comment 12 Larry the Git Cow 2019-02-23 19:56:56 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a3fd78857131a73df78d2724de425dc1610c342e

commit a3fd78857131a73df78d2724de425dc1610c342e
Author:     Matthew Thode <[e-mail]>
AuthorDate: 2019-02-23 19:52:49 +0000
Commit:     Matthew Thode <[e-mail]>
CommitDate: 2019-02-23 19:56:44 +0000

    media-sound/pulseeffects: define gcc minimum
    
    Bug: https://bugs.gentoo.org/678600
    Package-Manager: Portage-2.3.51, Repoman-2.3.12
    Signed-off-by: Matthew Thode <[e-mail]>

 media-sound/pulseeffects/pulseeffects-9999.ebuild | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)