kde4: compile error in systemsettings

[yodo]

Hey,
I just try to install KDE 4.0, but everytime emerge wants to compile "systemsettings-4.0.0" it stops with an error.
----> http://www.onlyfree.de/php/pasteservice/show.php?id=5988
I already searched in the internet, but did not find something usable...
Any idea?
greetings, yodo

[yodo]

*push* No one?!

[wrc1944]

Other than:

[bunder]

Moved from Desktop Environments to Unsupported Software.
_________________

[yodo]

[wrc1944]

Systemsettings is in workspace, which is in kdebase, which won't build unless qt, kdelibs, and kdepimlibs are first built with the needed USE flags (at least on SVN). Since systemsettings is actually a part of kdebase, I assume it needs the same USE flags, and all the others I mentioned need to be done first, before trying to compile anything in kdebase.

Look at my post here https://forums.gentoo.org/viewtopic-t-656051.html These work for me- I suggest you use them too.

Lines 354 and on indicate errors with kdm, leading into the final 557-558 failure point. Don't know what your qt & kdelibs USE flags are in /etc/package.use, or if fixing them will help, but that's where I'd start. If they aren't like I posted, it's a good bet adding them will let all the split kdebase packages compile. Keep us updated if this works, or not.

Update: Maybe the ebuilds are updated to include more USE flags- don't know about 4.0 versions, as I'm using SVN.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

[yodo]

Hm... I installed qt, kdelibs and kdepimlibs now with the USE flags you suggested in the linked thread.
Those three packages are successfuly installed now - but I still get the same error while installing systemsettings.
kdebase can't be installed because of blocked packages (e.g. libplasma). Don't really understand that... plasma belongs to KDE4...

[wrc1944]

Hmmm..- I don't get this either. Does it error out at exactly the same point as before, or does it get further?

One thought- are you possibly trying to mix 4.0-mono with 4.0 mixed? I know that's OK with kde3, but maybe not yet with kde4?

I guess all the correct USE flags sould be in all the split 4.0 ebuilds, but maybe they missed something. It's easier with the mono SVN versions I'm using, and might be easier figuring this stuff out with the mono 4.0's than with having to contend with all the split 4.0's.

Another thought- are you synced and updated in portage (and have run-uD world), and layman -s kde, and after that have you run emerge --regen, like the emerge overlay warning says?

Oh wait- maybe you're using the 4.0's in regular portage- correct?

I looked at the libplasma ebuld, and it is over 2 weeks old. Have you been following this thread related to 4.0 in portage? https://forums.gentoo.org/viewtopic-t-639443.html Maybe there's something there to help- I think this thread (and parts 1,2, and 3) is more layman kde overlay related.
EDIT: Another thought- you might try deleting the specific 4.0 source file in distfiles, and re-downloading fresh copy- (maybe it was corrupted and/or it's fixed there), and a revdep-rebuild -p to check if anything is in need of a rebuild.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

[yodo]

I followed this guide. I just kept on experimenting - everything seems to be installed correctly.

For KDE 3.5.8:

[Nick C]

cant remember if it works but try emerge -ep kde-base/kde-meta:kde-4, iirc that will try and rebuild ALL of kde4 and so in theory pull in any new dependencies that have since been added, look for any packages listed as N for new rather than R for rebuild then just go and emerge them manually.

**Note: i dont use portage anymore so emerge -e may be the wrong command to use
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved.
www.monkeydust.net

[yodo]

I will try that - but I'm afraid it will take VERY much time...

[yodo]

That did not help.

[yodo]

Fixed it by adding "kde-base/kde-meta:3.5.8" to the world file...
I know it should not be edited manually... but I don't know any other way. Why does that work anyway? "kde-meta:3.5.8" is not existing as a package.