Cannot build Clementine music player

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

I'm having trouble merging the latest Clementine. If anyone can help, I'd be very grateful. Here are the things:

jburns · Posted: Wed Sep 27, 2017 5:08 am Post subject:

After you emerged gcc-5.4.0 did you read the news item "GCC 5 Defaults to the New C++11 ABI" and rebuild packages using the new C++ ABI.

fedeliallalinea · Posted: Wed Sep 27, 2017 5:57 am Post subject:

You can post full build.log with wgetpaste?
_________________
Questions are guaranteed in life; Answers aren't.

asturm · Developer Joined: 05 Apr 2007 Posts: 8935

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

Thanks jburns. Wow... a news item from 2 years ago was relevant to this, but... I'm not eating and breathing my OS every day, so it's hard for me to track down such connections, much less be paying attention to them and remembering them over time. So, I tried to run the revdep-rebuild recommended in the news item:

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

jburns · Posted: Sat Sep 30, 2017 3:14 am Post subject:

Change "dev-cpp/libcmis:0" to "dev-cpp/libcmis:0.5". The slot number was changed.

fedeliallalinea · Posted: Sat Sep 30, 2017 8:17 am Post subject:

asturm · Developer Joined: 05 Apr 2007 Posts: 8935

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

fedeliallalinea · Posted: Sat Oct 07, 2017 11:41 am Post subject:

You tried with --backtrack=30 as portage suggest?
_________________
Questions are guaranteed in life; Answers aren't.

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

Thanks all. I have not succeeded with this yet, but have mostly been ignoring it for a while. I really need to get it fixed.

I tried updating the Qt stuff to 5.7.x, alone, with

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

Hang on... I tooled around a bit more and I think I've got the Big Rebuild running now.... will report back.

Punchcutter · Guru Joined: 11 Feb 2007 Posts: 354

Well, more fiddling led to things working out, as they always do, and I seem to be back on stable ground now. Thanks for the earlier help.
And thus, with yet another experience of fiddling around to get Portage to compile my system under my belt, I have now reached...
Guru status :lol:

radio_flyer · Posted: Tue Oct 31, 2017 2:07 am Post subject:

FYI, if anyone else ends up here with build failures in clementine around this date, it's a bug in stable QT4:

https://bugs.gentoo.org/635394

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

radio_flyer · Posted: Tue Oct 31, 2017 6:30 pm Post subject:

In general masking and unmasking packages (using /etc/portage/package.mask and /etc/portage/package.unmask respectively) is something you want to do with care, as that is the easiest way to get portage into an inconsistent state. In 15 years I have rarely had to use those files to resolve portage issues.

In this particular case the problem is that a broken development package made it into stable, which breaks the build of other stable packages. As per the bug link it appears the devs are aware of it and are attempting to get the next unstable version promoted to stable. Sometimes that process goes relatively fast (less than a day), other times it can take many days longer, depending on everything from whether there are other issues with the package to the relevant devs being on vacation or something.

Basically, when something is broken in stable like this you have two choices: wait however long for the broken package to be fixed, or stabilize a working version yourself by adding it to /etc/portage/package.accept_keywords. If the broken world update isn't borking my system in other ways, I typically just wait a day or two and attempt another world update to see if it got fixed in the meantime. Often it has been and I can just move on without doing anything other than thanking the devs for getting on it. If a day or two goes by with no fix, that's a good clue that the devs are busy elsewhere and I need to do something about it myself. In that case I do a quick bug search on the package marked for stabilization, and presuming Bugzilla isn't full of reports of it crashing and burning all the folks running unstable systems, I 'stabilize' it myself by adding it to accept_keywords. It's been a day, I've grown impatient, so a quick "=dev-qt/qtcore-4.8.7-r3" in package.accept_keywords has made portage happy and allowed my world update to complete. Tools like eix (eix-update;eix -Tt) and portpeek ('portpeek -ar') that I run after world updates tell me when the devs have finally stabilized the package and I can remove that line from my accept_keywords file.

Hope that helps.

lukipuki · Posted: Tue Oct 31, 2017 6:49 pm Post subject:

Hu · Moderator Joined: 06 Mar 2007 Posts: 21619

Rather than assuming what platform he is on, why not use the syntax that is platform agnostic? In package.accept_keywords, a bare package atom, with no architecture qualifiers, implies ~ARCH where ARCH is whatever is appropriate in context.

pourpier · Apprentice Joined: 27 Sep 2017 Posts: 166

radio_flyer · Posted: Thu Nov 02, 2017 5:25 pm Post subject: