Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[kde-testing] and [kde-crazy] KDE4 overlays thread (part 2)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 11, 12, 13 ... 28, 29, 30  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
aTan
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2007
Posts: 134
Location: Czech Republic (Ukraine)

PostPosted: Thu Nov 13, 2008 8:28 pm    Post subject: Reply with quote

wrc1944 wrote:
Thanks for the reply. :)
Still unclear as to your meaning- is it supposed to be:
Code:
KMEXTRACTONLY="config-runtime.h.kde4"
i.e., replace cmake with kde4?
Putting kde4 on another line is confusing. Replace line "a" with line "b" would be clearer.
Does this also apply to the 9999 ebuild? I'm running kdebase-live. The ebuilds are identical, except for the KEYWORDS= line.

I'm running 4.1.73. And I think that it will work for live ebuild. You can put kde4 on the same line separated by a space if it will look better for you but functionality will be the same.

Here is how that line could look like:
Code:
KMEXTRACTONLY="config-runtime.h.cmake kde4"
Back to top
View user's profile Send private message
cohone
Tux's lil' helper
Tux's lil' helper


Joined: 27 Mar 2006
Posts: 113

PostPosted: Thu Nov 13, 2008 8:41 pm    Post subject: Reply with quote

wrc1944 wrote:
Thanks for the reply. :)
Still unclear as to your meaning- is it supposed to be:
Code:
KMEXTRACTONLY="config-runtime.h.kde4"
i.e., replace cmake with kde4?
Putting kde4 on another line is confusing. Replace line "a" with line "b" would be clearer.
Does this also apply to the 9999 ebuild? I'm running kdebase-live. The ebuilds are identical, except for the KEYWORDS= line.


its not that way, just copy and paste from the 4.1.72 ebuild
Back to top
View user's profile Send private message
marcus84
Tux's lil' helper
Tux's lil' helper


Joined: 23 Apr 2008
Posts: 87

PostPosted: Thu Nov 13, 2008 8:45 pm    Post subject: Reply with quote

I get this error compiling ksirk 4.1.73
Any idea??


/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lqca
collect2: ld va retornar l'estat de sortida 1
make[2]: *** [lib/libiris_ksirk.so.2.0.0] Error 1
make[1]: *** [ksirk/ksirk/iris/src/CMakeFiles/iris_ksirk.dir/all] Error 2
make: *** [all] Error 2

* app-crypt/qca
Latest version available: 2.0.0-r2
Latest version installed: 2.0.0-r2
Size of files: 4,986 kB
Homepage: http://delta.affinix.com/qca/
Description: Qt Cryptographic Architecture (QCA)
License: LGPL-2
Back to top
View user's profile Send private message
earendilion
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2007
Posts: 115
Location: Meudon (92), France

PostPosted: Thu Nov 13, 2008 9:34 pm    Post subject: Reply with quote

Quote:

Do you have Hal started?


Sure :

Code:
earendil@gondor /usr/portage/local/layman/kde-crazy/kde-base $ sudo /etc/init.d/hald status
Password:
 * Caching service dependencies ...                                                                                                                    [ ok ]
 * status:  started
rendil@gondor /usr/portage/local/layman/kde-crazy/kde-base $ sudo /etc/init.d/hald status
Password:
 * Caching service dependencies ...                                                                                                                    [ ok ]
 * status:  started
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3234
Location: Gainesville, Florida

PostPosted: Thu Nov 13, 2008 10:34 pm    Post subject: Reply with quote

Hmmmm. I compiled the kdebase-live set, and kde-base/kdebase-data-9999 was the 3rd package. I didn't change anything in the ebuild, and it compiled fine, no problem. I did just finish a complete ~x86 system and world update first- maybe that made a difference. The kdebase-data-9999 ebuild does not have the kde4 on line 21-22, and apparently now doesn't need it, if indeed it did before.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.1.12-gentoo USE=experimental
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3234
Location: Gainesville, Florida

PostPosted: Thu Nov 13, 2008 11:35 pm    Post subject: Reply with quote

I was wondering if there are there plans for http://websvn.kde.org/trunk/extragear/ ebuilds any time soon. They seem more or less as up-to-date as other packages in trunk. There used to be some of these for kdesvn, like konq-plugins, etc, which worked fine before. Konqueror, as a web browser really needs those plugins- I've been going with firefox lately, after years of using konqueror, which I really miss in kdesvn. I was also using them when I was building kdesvn on Arch with the kdesvn-build tool, which worked fine.

Maybe I'll try writing an ebuild myself, but am not that confident about my ability to accomplish this. :roll:
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.29-r2, gcc-9.1.0 kernel-5.1.12-gentoo USE=experimental
Back to top
View user's profile Send private message
coolsnowmen
Veteran
Veteran


Joined: 30 Jun 2004
Posts: 1479
Location: No.VA

PostPosted: Fri Nov 14, 2008 2:20 am    Post subject: Reply with quote

Is there anyway to reduce collision_protect errors to warnings, or better yet, to prompts?
I'm getting tired of having to reemerge things because of a collision, but I like knowing when they occur (in case something breaks).


EDIT:
Current errors
-------------------------------------------------------
kde-base/ksirk-4.1.73:
[ 59%] Building CXX object ksirk/ksirk/iris/src/CMakeFiles/iris_ksirk.dir/iris_ksirk_automoc.o
Linking CXX shared library ../../../../lib/libiris_ksirk.so
/usr/lib/gcc/i686-pc-linux-gnu/4.2.4/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca

kde-base/kopete-4.1.73, same as ksirk
kde-base/okular-4.1.73 same as ksirk
_________________
emerge: there are no ebuilds to satisfy "moo"


Last edited by coolsnowmen on Fri Nov 14, 2008 5:12 pm; edited 1 time in total
Back to top
View user's profile Send private message
rahulthewall
Veteran
Veteran


Joined: 01 Nov 2007
Posts: 1264
Location: Zürich

PostPosted: Fri Nov 14, 2008 11:23 am    Post subject: Reply with quote

Kopete and okular (both - 4.1.73) are not compiling - errors related to qca.

Code:

Linking CXX shared module ../../../lib/okularGenerator_ooo.so                 
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/okularGenerator_ooo.so] Error 1                             
make[1]: *** [okular/generators/ooo/CMakeFiles/okularGenerator_ooo.dir/all] Error 2


Code:

Linking CXX shared library ../../../../lib/libiris_kopete.so                   
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/libiris_kopete.so.1.0.0] Error 1                             
make[1]: *** [kopete/protocols/jabber/libiris/CMakeFiles/iris_kopete.dir/all] Error 2


Downgrading qca or resyncing the tree did not help!
_________________
Who shall guard the guards?
Back to top
View user's profile Send private message
rahulthewall
Veteran
Veteran


Joined: 01 Nov 2007
Posts: 1264
Location: Zürich

PostPosted: Fri Nov 14, 2008 11:31 am    Post subject: Reply with quote

KDE freezes when I try to add a widget on the desktop. (4.1.73)
_________________
Who shall guard the guards?
Back to top
View user's profile Send private message
gimpel
Advocate
Advocate


Joined: 15 Oct 2004
Posts: 2720
Location: Munich, Bavaria

PostPosted: Fri Nov 14, 2008 12:12 pm    Post subject: Reply with quote

rahulthewall3000 wrote:
Kopete and okular (both - 4.1.73) are not compiling - errors related to qca.

Code:

Linking CXX shared module ../../../lib/okularGenerator_ooo.so                 
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/okularGenerator_ooo.so] Error 1                             
make[1]: *** [okular/generators/ooo/CMakeFiles/okularGenerator_ooo.dir/all] Error 2


Code:

Linking CXX shared library ../../../../lib/libiris_kopete.so                   
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/libiris_kopete.so.1.0.0] Error 1                             
make[1]: *** [kopete/protocols/jabber/libiris/CMakeFiles/iris_kopete.dir/all] Error 2


Downgrading qca or resyncing the tree did not help!

No idea how I got it working on the system with paludis/kde4-experimental... On this new one I just did
Code:
ln -s /usr/lib/qca2/libqca.so /usr/lib/libqca.so

as a temporary hack.
Seems that cmake/whatever doesn't take the settings from /etc/env.d/44qca2 nor /usr/lib/pkgconfig/qca2.pc
_________________
http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
Back to top
View user's profile Send private message
marcus84
Tux's lil' helper
Tux's lil' helper


Joined: 23 Apr 2008
Posts: 87

PostPosted: Fri Nov 14, 2008 1:59 pm    Post subject: Reply with quote

gimpel wrote:
rahulthewall3000 wrote:
Kopete and okular (both - 4.1.73) are not compiling - errors related to qca.

Code:

Linking CXX shared module ../../../lib/okularGenerator_ooo.so                 
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/okularGenerator_ooo.so] Error 1                             
make[1]: *** [okular/generators/ooo/CMakeFiles/okularGenerator_ooo.dir/all] Error 2


Code:

Linking CXX shared library ../../../../lib/libiris_kopete.so                   
/usr/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lqca                                                                 
collect2: ld returned 1 exit status                                           
make[2]: *** [lib/libiris_kopete.so.1.0.0] Error 1                             
make[1]: *** [kopete/protocols/jabber/libiris/CMakeFiles/iris_kopete.dir/all] Error 2


Downgrading qca or resyncing the tree did not help!

No idea how I got it working on the system with paludis/kde4-experimental... On this new one I just did
Code:
ln -s /usr/lib/qca2/libqca.so /usr/lib/libqca.so

as a temporary hack.
Seems that cmake/whatever doesn't take the settings from /etc/env.d/44qca2 nor /usr/lib/pkgconfig/qca2.pc


It works!!!

Here I post the next error I encountered:
Code:

mv: ha fallat stat() sobre <<kdegames-4.1.73>>: The file or directory doesn't exist
*
* ERROR: kde-base/ksquares-4.1.73 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 3628: Called kde4-meta_src_unpack
* environment, line 2892: Called kde4-meta_src_extract
* environment, line 2824: Called die
* The specific snippet of code:
* mv ${KMNAME}-${PV} ${P} || die "Died while moving "${KMNAME}-${PV}" to "${P}";
Back to top
View user's profile Send private message
coolsnowmen
Veteran
Veteran


Joined: 30 Jun 2004
Posts: 1479
Location: No.VA

PostPosted: Fri Nov 14, 2008 5:35 pm    Post subject: Reply with quote

@marcus84, sync your overlay,

AFAIK, all non "-lqca" ebuild errors are fixed.
_________________
emerge: there are no ebuilds to satisfy "moo"


Last edited by coolsnowmen on Fri Nov 14, 2008 7:21 pm; edited 1 time in total
Back to top
View user's profile Send private message
angiest
n00b
n00b


Joined: 12 Nov 2008
Posts: 14

PostPosted: Fri Nov 14, 2008 6:43 pm    Post subject: Reply with quote

I fixed the compile for okular in kde-crazy by modifying the src_configure() function in the ebuild to include:
Code:
       if use crypt; then
                        mycmakeargs="${mycmakeargs}
                        -DQCA2_LIBRARIES=/usr/$(get_libdir)/qca2/libqca.so.2"
                fi


This should fix the other ebuilds as well. I will try this on Kopete soon. What is the proper way to report this to the maintainers? :)
Back to top
View user's profile Send private message
angiest
n00b
n00b


Joined: 12 Nov 2008
Posts: 14

PostPosted: Fri Nov 14, 2008 6:45 pm    Post subject: Reply with quote

coolsnowmen wrote:
@marcus84, sync your overlay,

AFAIK, all non "-lqca" ebuild errors are fixes.


Doh! Should have checked the forum again before posting after being away for a long time.
Back to top
View user's profile Send private message
coolsnowmen
Veteran
Veteran


Joined: 30 Jun 2004
Posts: 1479
Location: No.VA

PostPosted: Fri Nov 14, 2008 7:16 pm    Post subject: Reply with quote

angiest wrote:
coolsnowmen wrote:
@marcus84, sync your overlay,

AFAIK, all non "-lqca" ebuild errors are fixes.


Doh! Should have checked the forum again before posting after being away for a long time.

Apparently I wrote that confusingly,
The only errors I still get are -lqca related, your fix may very well be useful.
I was referring to the unpacking errors.
_________________
emerge: there are no ebuilds to satisfy "moo"
Back to top
View user's profile Send private message
angiest
n00b
n00b


Joined: 12 Nov 2008
Posts: 14

PostPosted: Fri Nov 14, 2008 7:18 pm    Post subject: Reply with quote

coolsnowmen wrote:
angiest wrote:
coolsnowmen wrote:
@marcus84, sync your overlay,

AFAIK, all non "-lqca" ebuild errors are fixes.


Doh! Should have checked the forum again before posting after being away for a long time.

Apparently I wrote that confusingly,
The only errors I still get are -lqca related, your fix may very well be useful.
I was referring to the unpacking errors.


Trying to sneak this in while doing "real" work apparently lead me to read your post to quickly. I see now what you wrote quite plainly. :)
Back to top
View user's profile Send private message
hunky
l33t
l33t


Joined: 19 Nov 2003
Posts: 821
Location: Alaska

PostPosted: Sat Nov 15, 2008 4:34 am    Post subject: Reply with quote

I've been hankerin' to give KDE-4.2 a try but not really ready to dive in because I haven't really read anything but grief in this thread. Hopefully lots of folks are enjoying it and I'm only seeing the few with problems? Anyway - I have a question that might be simple to answer:

I thought before I jumped in I would at least get set up. So I keyworded (~x86) portage and got the latest of that. I installed the overlay kde-crazy and linked the package unmask and keywords from there to my /etc/portage/.. directories. That caused lots of qt blockers which I resolved, and then emerged all the qt stuff that wanted to get pulled in. That was all fine until I did a layman -S. Now when I do emerge -avuD world, I'm getting lots of new packages wanting keywording and it looks like it is going to pull in something I'm not yet asking for - I assume kde4 but not sure. It is saying for example:
Code:
Calculating dependencies... done!

!!! All ebuilds that could satisfy ">=dev-cpp/pangomm-2.14.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-cpp/pangomm-2.14.1 (masked by: ~x86 keyword)
- dev-cpp/pangomm-2.14.0 (masked by: ~x86 keyword)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
(dependency required by "dev-cpp/gtkmm-2.14.3" [ebuild])
(dependency required by "media-sound/ardour-2.6.1_p4010" [ebuild])
(dependency required by "@world" [argument])

I've already keyworded glibmm, libical, libzip, and add USE flag "accessibility" to gtkmm. I don't know when it will stop - I could be here all night keywording files or it may be about done - no idea. But what is @world? I've read a bit about sets for kde4 but I would have figured that it wouldn't pull anything in until I specifically asked to emerge kde4. (I'm currently running kde3.5.9).

Do I need to remove the kde-crazy to get back to before this last layman sync?
If I decide to go for kde4, do I need to upgrade kde3.5.9 to 3.5.10? And do I need to add kdeprefix to my make.conf USE flags or perhaps -kdeprefix? Not quite clear on what would be best there.

If I decide to go for it, I'm assuming I can still use my fav programs like digikam, qjackctl, k3b, etc.. I'm guessing these are working. I use Amarok but if it is problematic can live without it.

Sorry for all the questions but really curious about this stuff - been wading through these threads and it doesn't seem like I should go for it yet but have been playing around with it on Kubuntu in a virtualbox machine and it seems ok there. o

Many thanks - cheers, JD

[edit] well, while awaiting a response I went ahead and keyworded pangomm and on the next emerge try - kdelibs:4.2[-kdeprefix] showed up - so I guess it is trying to pull in kde4.2. I'll not proceed until I have a better understanding..
Back to top
View user's profile Send private message
earendilion
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2007
Posts: 115
Location: Meudon (92), France

PostPosted: Sat Nov 15, 2008 8:50 am    Post subject: Reply with quote

Compiling dolphin fails, complaining that it don"t find some files. So I extracted these files from the kdebase distfile, and compied it to the work folder ... But then, I get this error :

Code:
[ 71%] Building CXX object apps/dolphin/src/CMakeFiles/dolphin.dir/dolphincontextmenu.o                                                                     
In file included from /var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphinviewcontainer.cpp:56:                             
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.h:27:29: error: konq_copytomenu.h: No such file or directory
In file included from /var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.cpp:21:                               
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.h:27:29: error: konq_copytomenu.h: No such file or directory
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.h:123: error: 'KonqCopyToMenu' does not name a type         
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.cpp: In member function 'void DolphinContextMenu::openItemContextMenu()':
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.cpp:208: error: 'm_copyToMenu' was not declared in this scope
make[2]: *** [apps/dolphin/src/CMakeFiles/dolphin.dir/dolphincontextmenu.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/var/tmp/portage/kde-base/dolphin-4.1.73/work/dolphin-4.1.73/apps/dolphin/src/dolphincontextmenu.h:123: error: 'KonqCopyToMenu' does not name a type
make[2]: *** [apps/dolphin/src/CMakeFiles/dolphin.dir/dolphinviewcontainer.o] Error 1
make[1]: *** [apps/dolphin/src/CMakeFiles/dolphin.dir/all] Error 2
make: *** [all] Error 2


Has anyone had this problem ?
Back to top
View user's profile Send private message
marcus84
Tux's lil' helper
Tux's lil' helper


Joined: 23 Apr 2008
Posts: 87

PostPosted: Sat Nov 15, 2008 10:33 am    Post subject: Reply with quote

hunky wrote:
I've been hankerin' to give KDE-4.2 a try but not really ready to dive in because I haven't really read anything but grief in this thread. Hopefully lots of folks are enjoying it and I'm only seeing the few with problems? Anyway - I have a question that might be simple to answer:

I thought before I jumped in I would at least get set up. So I keyworded (~x86) portage and got the latest of that. I installed the overlay kde-crazy and linked the package unmask and keywords from there to my /etc/portage/.. directories. That caused lots of qt blockers which I resolved, and then emerged all the qt stuff that wanted to get pulled in. That was all fine until I did a layman -S. Now when I do emerge -avuD world, I'm getting lots of new packages wanting keywording and it looks like it is going to pull in something I'm not yet asking for - I assume kde4 but not sure. It is saying for example:
Code:
Calculating dependencies... done!

!!! All ebuilds that could satisfy ">=dev-cpp/pangomm-2.14.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-cpp/pangomm-2.14.1 (masked by: ~x86 keyword)
- dev-cpp/pangomm-2.14.0 (masked by: ~x86 keyword)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
(dependency required by "dev-cpp/gtkmm-2.14.3" [ebuild])
(dependency required by "media-sound/ardour-2.6.1_p4010" [ebuild])
(dependency required by "@world" [argument])

I've already keyworded glibmm, libical, libzip, and add USE flag "accessibility" to gtkmm. I don't know when it will stop - I could be here all night keywording files or it may be about done - no idea. But what is @world? I've read a bit about sets for kde4 but I would have figured that it wouldn't pull anything in until I specifically asked to emerge kde4. (I'm currently running kde3.5.9).

Do I need to remove the kde-crazy to get back to before this last layman sync?
If I decide to go for kde4, do I need to upgrade kde3.5.9 to 3.5.10? And do I need to add kdeprefix to my make.conf USE flags or perhaps -kdeprefix? Not quite clear on what would be best there.

If I decide to go for it, I'm assuming I can still use my fav programs like digikam, qjackctl, k3b, etc.. I'm guessing these are working. I use Amarok but if it is problematic can live without it.

Sorry for all the questions but really curious about this stuff - been wading through these threads and it doesn't seem like I should go for it yet but have been playing around with it on Kubuntu in a virtualbox machine and it seems ok there. o

Many thanks - cheers, JD

[edit] well, while awaiting a response I went ahead and keyworded pangomm and on the next emerge try - kdelibs:4.2[-kdeprefix] showed up - so I guess it is trying to pull in kde4.2. I'll not proceed until I have a better understanding..


You can have kde-3.5.9 and kde4 at the same time, but for this you should use the 'kdeprefix' USE which will install kde4.2 in /usr/kde4.2 folder.
Back to top
View user's profile Send private message
tampakrap
Retired Dev
Retired Dev


Joined: 27 Nov 2007
Posts: 71
Location: Prague, Czech Republic

PostPosted: Sat Nov 15, 2008 11:00 am    Post subject: Reply with quote

Some of the maintainers of the live ebuilds, more specifically krytzz, Sput, reavertm and me, have been called by scarabeus to join kde herd arch testers. This will give us access to overlays (gah), and also access to edit bugs in bugzilla (more bug-wranglers == less bugs :) ) So please be patient if we will be less active as we have to finish the ebuild quiz...
Back to top
View user's profile Send private message
marcus84
Tux's lil' helper
Tux's lil' helper


Joined: 23 Apr 2008
Posts: 87

PostPosted: Sat Nov 15, 2008 12:07 pm    Post subject: Reply with quote

Compiling pykde-4.1.73 I get the following errors where linking:

Linking CXX shared library ../../lib/pykde/plasma.so
CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart0.o: In function `void
* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Containment::StyleOp
tion const*)':
sipplasmapart0.cpp:(.text._Z24qMetaTypeConstructHelperIN6Plasma11Containment11StyleOption
EEPvPKT_[void* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Contain
ment::StyleOption const*)]+0x2a): undefined reference to `Plasma::Containment::StyleOptio
n::StyleOption(Plasma::Containment::StyleOption const&)'
sipplasmapart0.cpp:(.text._Z24qMetaTypeConstructHelperIN6Plasma11Containment11StyleOption
EEPvPKT_[void* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Contain
ment::StyleOption const*)]+0x51): undefined reference to `Plasma::Containment::StyleOptio
n::StyleOption()'
CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart6.o: In function `init
_Plasma_Containment_StyleOption':
sipplasmapart6.cpp:(.text+0x4934): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption(QStyleOptionGraphicsItem const&)'
sipplasmapart6.cpp:(.text+0x495b): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption()'
sipplasmapart6.cpp:(.text+0x4993): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption(Plasma::Containment::StyleOption const&)'
collect2: ld va retornar l'estat de sortida 1
make[2]: *** [lib/pykde/plasma.so] Error 1
make[1]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/all] Error 2
make: *** [all] Error 2
*
* ERROR: kde-base/pykde4-4.1.73 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3559: Called kde4-meta_src_compile
* environment, line 2723: Called kde4-meta_src_make
* environment, line 2816: Called kde4-base_src_make
* environment, line 2454: Called cmake-utils_src_make
* environment, line 899: Called die
* The specific snippet of code:
* emake "$@" || die "Make failed!";
* The die message:
* Make failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/home/tmp_portage/portage/kde-base/pykde4-4.1.73/t
emp/build.log'.
* The ebuild environment file is located at '/home/tmp_portage/portage/kde-base/pykde4-4
.1.73/temp/environment'.
* This ebuild used the following eclasses from overlays:
* /usr/portage/local/layman/kde-crazy/eclass/kde4-meta.eclass
* /usr/portage/local/layman/kde-crazy/eclass/kde4-functions.eclass
* /usr/portage/local/layman/kde-crazy/eclass/kde4-base.eclass
*
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1159

PostPosted: Sat Nov 15, 2008 12:16 pm    Post subject: Reply with quote

from yesterday everything compiles but then kded4 and
plasma-workspace crashes. anybody with same problem?


EDIT:
SOLVED
needed digikam and it installed a different kdelibs
which conflicted with the kdelibs:live
_________________
this is a strange strange world.


Last edited by tranquilcool on Sat Nov 15, 2008 11:54 pm; edited 1 time in total
Back to top
View user's profile Send private message
cracki
n00b
n00b


Joined: 12 Oct 2005
Posts: 34

PostPosted: Sat Nov 15, 2008 4:03 pm    Post subject: Reply with quote

Hi,
I updated from the old overlay to kde-crazy, now I cant even emerge world...
Any ideas?
:?
Code:
emerge world -DvauN
emerge: the given set 'world' contains a non-existent set named 'kde-svn-minimal'


and

Code:
emerge -Cav @kde-svn-minimal
emerge: There are no sets to satisfy 'kde-svn-minimal'
Back to top
View user's profile Send private message
coolsnowmen
Veteran
Veteran


Joined: 30 Jun 2004
Posts: 1479
Location: No.VA

PostPosted: Sat Nov 15, 2008 4:11 pm    Post subject: Reply with quote

marcus84 wrote:
hunky wrote:
...

[edit] well, while awaiting a response I went ahead and keyworded pangomm and on the next emerge try - kdelibs:4.2[-kdeprefix] showed up - so I guess it is trying to pull in kde4.2. I'll not proceed until I have a better understanding..


You can have kde-3.5.9 and kde4 at the same time, but for this you should use the 'kdeprefix' USE which will install kde4.2 in /usr/kde4.2 folder.


It would seem like a good idea, but can anyone give me a reason why kdeprefix is necessary for parallel 3.5 and Versions > 4

I don't use kdeprefix and my kde 4.2 things get installed to

/usr/bin/ (vs /usr/kde/3.5/bin/)
/usr/include/KDE/ (vs /usr/kde/3.5/include/)
/usr/kde/4.2 (vs /usr/kde/3.5/)
/usr/lib/kde4/ (vs /usr/kde/3.5/lib/)

It seems that my kde 3.5 things are pretty out of the way. Segmenting my 4.2 stuff would only help me install parallel versions of kde4.1 and kde4.2
_________________
emerge: there are no ebuilds to satisfy "moo"
Back to top
View user's profile Send private message
marcus84
Tux's lil' helper
Tux's lil' helper


Joined: 23 Apr 2008
Posts: 87

PostPosted: Sat Nov 15, 2008 5:13 pm    Post subject: Reply with quote

marcus84 wrote:
Compiling pykde-4.1.73 I get the following errors where linking:

Linking CXX shared library ../../lib/pykde/plasma.so
CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart0.o: In function `void
* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Containment::StyleOp
tion const*)':
sipplasmapart0.cpp:(.text._Z24qMetaTypeConstructHelperIN6Plasma11Containment11StyleOption
EEPvPKT_[void* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Contain
ment::StyleOption const*)]+0x2a): undefined reference to `Plasma::Containment::StyleOptio
n::StyleOption(Plasma::Containment::StyleOption const&)'
sipplasmapart0.cpp:(.text._Z24qMetaTypeConstructHelperIN6Plasma11Containment11StyleOption
EEPvPKT_[void* qMetaTypeConstructHelper<Plasma::Containment::StyleOption>(Plasma::Contain
ment::StyleOption const*)]+0x51): undefined reference to `Plasma::Containment::StyleOptio
n::StyleOption()'
CMakeFiles/python_module_PyKDE4_plasma.dir/sip/plasma/sipplasmapart6.o: In function `init
_Plasma_Containment_StyleOption':
sipplasmapart6.cpp:(.text+0x4934): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption(QStyleOptionGraphicsItem const&)'
sipplasmapart6.cpp:(.text+0x495b): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption()'
sipplasmapart6.cpp:(.text+0x4993): undefined reference to `Plasma::Containment::StyleOpti
on::StyleOption(Plasma::Containment::StyleOption const&)'
collect2: ld va retornar l'estat de sortida 1
make[2]: *** [lib/pykde/plasma.so] Error 1
make[1]: *** [python/pykde4/CMakeFiles/python_module_PyKDE4_plasma.dir/all] Error 2
make: *** [all] Error 2
*
* ERROR: kde-base/pykde4-4.1.73 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3559: Called kde4-meta_src_compile
* environment, line 2723: Called kde4-meta_src_make
* environment, line 2816: Called kde4-base_src_make
* environment, line 2454: Called cmake-utils_src_make
* environment, line 899: Called die
* The specific snippet of code:
* emake "$@" || die "Make failed!";
* The die message:
* Make failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/home/tmp_portage/portage/kde-base/pykde4-4.1.73/t
emp/build.log'.
* The ebuild environment file is located at '/home/tmp_portage/portage/kde-base/pykde4-4
.1.73/temp/environment'.
* This ebuild used the following eclasses from overlays:
* /usr/portage/local/layman/kde-crazy/eclass/kde4-meta.eclass
* /usr/portage/local/layman/kde-crazy/eclass/kde4-functions.eclass
* /usr/portage/local/layman/kde-crazy/eclass/kde4-base.eclass
*



Any idea???
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3 ... 11, 12, 13 ... 28, 29, 30  Next
Page 12 of 30

 
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