Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
amarok-2.4.0 emerge failing building amarok_service_jamendo
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1070
Location: Stuart, Florida

PostPosted: Wed Dec 14, 2011 4:15 pm    Post subject: amarok-2.4.0 emerge failing building amarok_service_jamendo Reply with quote

I am going through the dance to get my system stabilized after my last emerge --update and amarok is failing to emerge. This system is running kde 4.7.4 on an amd64 system.


    Scanning dependencies of target amarok_service_jamendo
    Scanning dependencies of target amarok_service_magnatunestore
    [ 91%] Building CXX object src/context/containments/verticallayout/CMakeFiles/amarok_containment_vertical.dir/VerticalAppletLayout.o
    In file included from /var/tmp/portage/media-sound/amarok-2.4.0/work/amarok-2.4.0/src/context/scriptengine/javascript/simplejavascriptapplet.cpp:42:0:
    /var/tmp/portage/media-sound/amarok-2.4.0/work/amarok-2.4.0/src/context/scriptengine/javascript/bind_dataengine.h:32:1: error: redefinition of âstruct QMetaTypeId<Plasma::Service*>â
    /usr/include/plasma/service.h:321:1: error: previous definition of âstruct QMetaTypeId<Plasma::Service*>â
    /var/tmp/portage/media-sound/amarok-2.4.0/work/amarok-2.4.0/src/context/scriptengine/javascript/bind_dataengine.h:33:1: error: redefinition of âstruct QMetaTypeId<Plasma::ServiceJob*>â
    /usr/include/KDE/Plasma/../../plasma/servicejob.h:136:1: error: previous definition of âstruct QMetaTypeId<Plasma::ServiceJob*>â
    [ 91%] Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/amarok_service_jamendo_automoc.o
    make[2]: *** [src/context/scriptengine/javascript/CMakeFiles/amarok_appletscript_simple_javascript.dir/simplejavascriptapplet.o] Error 1
    make[1]: *** [src/context/scriptengine/javascript/CMakeFiles/amarok_appletscript_simple_javascript.dir/all] Error 2
    make[1]: *** Waiting for unfinished jobs....
    [ 91%] Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/JamendoService.o
    Linking CXX shared module ../../../../lib/amarok_data_engine_tabs.so
    [ 91%] Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/JamendoMeta.o
    [ 91%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/amarok_service_magnatunestore_automoc.o
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneActions.o
    [ 92%] Built target amarok_data_engine_tabs
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneAlbumDownloader.o
    Linking CXX shared module ../../../../lib/amarok_containment_vertical.so
    [ 92%] Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/JamendoDatabaseHandler.o
    [ 92%] Built target amarok_containment_vertical
    [ 92%] [ 92%] Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/JamendoXmlParser.o
    Building CXX object src/services/jamendo/CMakeFiles/amarok_service_jamendo.dir/JamendoInfoParser.o
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneCollectionLocation.o
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneConfig.o
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneDatabaseHandler.o
    [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneDatabaseWorker.o
    [ 92%] [ 92%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneDownloadInfo.o
    Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneDownloadDialog.o
    Linking CXX shared module ../../../lib/amarok_service_jamendo.so
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneInfoParser.o
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneMeta.o
    [ 93%] Built target amarok_service_jamendo
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneDownloadHandler.o
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneRedownloadDialog.o
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneRedownloadHandler.o
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneSqlCollection.o
    [ 93%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneStore.o
    [ 94%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneUrlRunner.o
    [ 94%] Building CXX object src/services/magnatune/CMakeFiles/amarok_service_magnatunestore.dir/MagnatuneXmlParser.o
    Linking CXX shared module ../../../lib/amarok_service_magnatunestore.so
    [ 94%] Built target amarok_service_magnatunestore
    make: *** [all] Error 2
    emake failed
    * ERROR: media-sound/amarok-2.4.0 failed (compile phase):
    * Make failed!
    *
    * Call stack:
    * ebuild.sh, line 56: Called src_compile
    * environment, line 4150: Called kde4-base_src_compile
    * environment, line 3237: Called cmake-utils_src_compile
    * environment, line 1417: Called _execute_optionaly 'src_compile'
    * environment, line 774: Called enable_cmake-utils_src_compile
    * environment, line 1698: Called cmake-utils_src_make
    * environment, line 1436: Called die
    * The specific snippet of code:
    * emake "$@" || die "Make failed!";
    *
    * If you need support, post the output of 'emerge --info =media-sound/amarok-2.4.0',
    * the complete build log and the output of 'emerge -pqv =media-sound/amarok-2.4.0'.
    * The complete build log is located at '/var/tmp/portage/media-sound/amarok-2.4.0/temp/build.log'.
    * The ebuild environment file is located at '/var/tmp/portage/media-sound/amarok-2.4.0/temp/environment'.
    * S: '/var/tmp/portage/media-sound/amarok-2.4.0/work/amarok-2.4.0'

    >>> Failed to emerge media-sound/amarok-2.4.0, Log file:

    >>> '/var/tmp/portage/media-sound/amarok-2.4.0/temp/build.log'
Back to top
View user's profile Send private message
hasufell
Retired Dev
Retired Dev


Joined: 29 Oct 2011
Posts: 429

PostPosted: Wed Dec 14, 2011 4:36 pm    Post subject: Reply with quote

i think you somehow mixed unstable with stable

latest amarok is 2.4.3

not sure if that will solve your issue though...
Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1070
Location: Stuart, Florida

PostPosted: Wed Dec 14, 2011 5:23 pm    Post subject: Reply with quote

I hear you, but see below:


    bopper etc # emerge amarok -p

    These are the packages that would be merged, in order:

    Calculating dependencies... done!
    [ebuild R ] media-sound/amarok-2.4.0 LINGUAS="-es*"
    bopper etc # ACCEPT_KEYWORDS="~amd64" emerge amarok -p

    These are the packages that would be merged, in order:

    Calculating dependencies... done!
    [ebuild U ] media-sound/amarok-2.4.3 [2.4.0] LINGUAS="-es*"
    bopper etc #
Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1070
Location: Stuart, Florida

PostPosted: Wed Dec 14, 2011 5:28 pm    Post subject: Reply with quote

It is interesting that I put an akonadi entry in package.keywords.newkde and it didn't work, but it did when I put it in package.keywords.
Back to top
View user's profile Send private message
hasufell
Retired Dev
Retired Dev


Joined: 29 Oct 2011
Posts: 429

PostPosted: Wed Dec 14, 2011 5:37 pm    Post subject: Reply with quote

http://dev.gentoo.org/~zmedico/portage/doc/man/portage.5.html

try /etc/portage/package.accept_keywords/newkde

Quote:
The package.accept_keywords file is intended to replace the package.keywords file, since profiles support a different form of package.keywords which modifies effective KEYWORDS (rather than ACCEPT_KEYWORDS).


does 2.4.3 compile now?
Back to top
View user's profile Send private message
MattMurdock
n00b
n00b


Joined: 27 Dec 2011
Posts: 4

PostPosted: Tue Dec 27, 2011 11:18 am    Post subject: Reply with quote

Getting the exact same error when emerging amarok on KDE 4.7.3 on an amd64 machine. I'm rather new to Gentoo; could you please detail exactly how you solved this problem?
Cheers
Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1070
Location: Stuart, Florida

PostPosted: Tue Dec 27, 2011 2:01 pm    Post subject: Reply with quote

It goes without saying that you identified amarok as the problem based on the error messages.

Usually the keyworded versions are the candidate releasable versions of the program, so they are an obvious choice as a solution. I would have tried this, except that I was thinking that the release version should have compiled...

I put the new version of amarok into /etc/portage/package.keywords.newkde. This should have worked. When I still had the same problem and amarok-2.4.0 was still being compiled, I put the entry into /etc/portage/package.keywords. This is the original version of the file, and I decided that portage might not work as advertised...
Back to top
View user's profile Send private message
gentooP4
Apprentice
Apprentice


Joined: 20 Sep 2010
Posts: 182
Location: NZ

PostPosted: Tue Dec 27, 2011 6:42 pm    Post subject: Reply with quote

I am getting a similar error for Virtualbox as well as the one above for Amarok

Virtualbox...
Code:
* ERROR: app-emulation/virtualbox-4.1.4 failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of 'emerge --info =app-emulation/virtualbox-4.1.4',
 * the complete build log and the output of 'emerge -pqv =app-emulation/virtualbox-4.1.4'.
 * The complete build log is located at '/var/tmp/portage/app-emulation/virtualbox-4.1.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/virtualbox-4.1.4/temp/environment'.
 * S: '/var/tmp/portage/app-emulation/virtualbox-4.1.4/work/VirtualBox-4.1.4_OSE'


Both indicating emake/make failed. Does anyone know if they are related as part of a bigger issue?

Thanks
_________________
The United States has announced that it will deploy thoughts and prayers in the battle against online extremism.

If you voted for Trump or Brexit, you were likely influenced by the Cambridge Analytica propaganda machine.
Back to top
View user's profile Send private message
MattMurdock
n00b
n00b


Joined: 27 Dec 2011
Posts: 4

PostPosted: Tue Dec 27, 2011 11:34 pm    Post subject: Reply with quote

Workaround was to install Amarok 2.5.0 with
Code:
$ ACCEPT_KEYWORDS="~amd64" emerge amarok

which compiled successfully. I'd rather use the stable release though if possible.

What is the akonadi entry you added to package.keywords?
Back to top
View user's profile Send private message
Featherfoot
Veteran
Veteran


Joined: 28 Dec 2002
Posts: 1070
Location: Stuart, Florida

PostPosted: Tue Dec 27, 2011 11:46 pm    Post subject: Reply with quote

I just made an amarok entry in /etc/portage/package.keywords

That applies the ~amd64 keyword to amarok.
Back to top
View user's profile Send private message
gentooP4
Apprentice
Apprentice


Joined: 20 Sep 2010
Posts: 182
Location: NZ

PostPosted: Wed Dec 28, 2011 10:40 pm    Post subject: Reply with quote

Amarok has compiled fine for me tonight. It pulled in version 2.4.3.

VB has also worked :)
_________________
The United States has announced that it will deploy thoughts and prayers in the battle against online extremism.

If you voted for Trump or Brexit, you were likely influenced by the Cambridge Analytica propaganda machine.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum