no1livz4ever
-
Posts
19 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by no1livz4ever
-
-
Sorry for the delay and bad quality ...
-
Here it is:
-
I will. I’m currently not at home, left my PC to compile KDE. Will post later.
-
Seems that I got past the problem. I set USE=“-rdoc” and RUBY_TARGETS=“ruby_21 .... 24”. Then i run emerge —autounmask-write plasma meta and updated etc. Seems to work ...
-
Trying with USE=“-rdoc”. Output is the same. Of course I’ve ran ego sync and emerge update before this ...
-
No luck. Here are the screenshots
-
Ok. I’ll try to remove -rdoc USE and emerge plasma-meta, I’ll post the result. Thanks for helping.
-
Yes. Currently it’s compiling because I’ve added kde-plasma-5 mix, but I’ll screenshot my conf file when it’s done.
-
Up until this step (emerging plasma-meta) everything went very smooth, installed X server, startx working, evdev input ok, during boot no errors, emerge —depclean nothing, nothing to update, i’ve synced ego few times ... cannot get past this error. Pretty frustrating because it took me almost a whole day to get to this step ...
-
-
I cannot bin paste, because it’s installing on a hard drive. I can take a screenshot only. It’s the same as member Mauricev stated in his post ...
-
No luck. I’ve added USE flag -rdoc and still getting the same conflict when trying to emerge plasma-meta ...
-
Thanks once again. I’ll try. It seems that I have to learn much more about the use of USE flags
-
I’ve chosen my stage 3 tarball as Intel Haswell, and set my flavor as desktop, installed X server and when I tried to emerge plasma-meta package only then this conflict appeared.
-
Yes, of course. I’ve only added my intel video card, all other flags were recognized by funtoo profile system as stated in install guide. I guess that’s why it was empty. Up until now I didn’t encounter any need to modify it.
-
This is global (portage) make.conf file? Mine is totally empty. I’ll try this, KDE installation was not possible due to mentionet ruby conflicts. Thanks. I’ll report later.
-
While trying to emerge plasma-meta package I’ve encountered the same conflicts regarding ruby ebuilds and cannot get past it. Did you manage to solve the conflict and how? Tnx
-
What did you exactly set? Did you set USE per package or globally? I’ve also encountered exactly the same problem and cannot get past it ... it would be great if you coukd post your USE settings for rdoc. Tnx
ruby blocking kde-plasma
in Installation Help
Posted
Thank you