| View previous topic :: View next topic |
| Author |
Message |
mreff555
Apprentice
Joined: 10 Mar 2011
Posts: 231
Location: Philadelphia
|
 Posted: Tue Jan 27, 2015 3:15 pm Post subject: systemd / KDE / appropriate build |
 |
|
I've installed gentoo many times before but generally with a much less involved profile. I generally just use openbox and I've never successfully installed systemd
I was originally trying to build a hardened KDE system running systemd, but I gave up on the hardened because I couldn't create a bootable kernel. (I've run into the same problem before)
as for KDE and systemd, I used the 'current-stage3-amd64'. As the instructions imply systemd was the first thing I tried to install after chrooting and I still get slot conflicts. I would be pointless to post error messages now because I've already trashed this build by unmerging a bunch of stuff.
Is there a different stage I should be starting with to get systemd installed? |
|
| Back to top |
|
 |
evetsnameloc
n00b
Joined: 14 Dec 2014
Posts: 26
Location: Colorado Springs, CO
|
| Posted: Tue Jan 27, 2015 3:21 pm Post subject: |
|
|
I used the same tarball to install gentoo, and have had no problem with KDE and systemd on two different computers. I selected the ".../kde/systemd" profile and systemd was installed correctly on my next "emerge -uDN @world". That should be all you need to do, at least for the systemd part. Make sure that you have systemd support enabled in your kernel (NOT the default setting, btw). You also need to enable it in your bootloader settings.
Last edited by evetsnameloc on Tue Jan 27, 2015 3:23 pm; edited 1 time in total |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Tue Jan 27, 2015 3:22 pm Post subject: |
|
|
Have you switched to a systemd profile?
7 like the one you should use.
| Code: | $ eselect profile list | grep systemd
[5] default/linux/amd64/13.0/desktop/gnome/systemd
[7] default/linux/amd64/13.0/desktop/kde/systemd
[12] default/linux/amd64/13.0/no-emul-linux-x86/desktop/gnome/systemd
[14] default/linux/amd64/13.0/no-emul-linux-x86/desktop/kde/systemd
|
|
|
| Back to top |
|
|
mreff555
Apprentice
Joined: 10 Mar 2011
Posts: 231
Location: Philadelphia
|
| Posted: Tue Jan 27, 2015 8:18 pm Post subject: |
|
|
Yes I selected 14, KDE and systemd
After this I built the kernel from a known good configuration, the only thing I changed was turning on the systemd flag.
Then, before rebooting I tried installing systemd, I was under the impression that I would need to install it before rebooting.
The only software I had installed prior to attempting systemd was 'linux-firmware' and 'lz4' which were needed to compile the kernel. |
|
| Back to top |
|
|
mreff555
Apprentice
Joined: 10 Mar 2011
Posts: 231
Location: Philadelphia
|
| Posted: Wed Jan 28, 2015 2:35 am Post subject: |
|
|
Alright. I tried it again
downloaded the stages again, and started all over.
followed the x86_64 instructions and after syncing I tried running 'emerge -avuDN --with-bdeps=y @world'
this is what I got
| Code: |
(chroot) sysresccd / # eselect profile set 14
(chroot) sysresccd / # emerge -avuDN --with-bdeps=y @world
setlocale: unsupported locale setting
* IMPORTANT: 8 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.
These are the packages that would be merged, in order:
Calculating dependencies... done!
!!! The ebuild selected to satisfy "=dev-db/mariadb-10.0*[embedded=,minimal=,static=,static-libs=,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" has unmet requirements.
- dev-db/mariadb-10.0.15-r1::gentoo USE="community pam perl ssl xml -cluster -debug -embedded -extraengine -jemalloc -latin1 -max-idx-128 -minimal -odbc -oqgraph -profiling (-selinux) -sphinx -static -static-libs -systemtap -tcmalloc -test -tokudb" ABI_X86="64 -32 -x32"
The following REQUIRED_USE flag constraints are unsatisfied:
xml? ( extraengine )
The above constraints are a subset of the following complete expression:
odbc? ( extraengine !minimal ) xml? ( extraengine !minimal ) minimal? ( !oqgraph !sphinx ) tokudb? ( jemalloc ) tcmalloc? ( !jemalloc ) jemalloc? ( !tcmalloc ) minimal? ( !cluster !extraengine !embedded ) static? ( !ssl )
(dependency required by "virtual/mysql-5.6-r2" [ebuild])
(dependency required by "dev-qt/qtsql-4.8.5[mysql]" [ebuild])
(dependency required by "dev-qt/qt3support-4.8.5" [ebuild])
(dependency required by "dev-qt/designer-4.8.5[qt3support]" [ebuild])
(dependency required by "kde-base/kdelibs-4.14.3-r1" [ebuild])
(dependency required by "media-video/vlc-2.1.2[kde]" [ebuild])
(dependency required by "media-libs/phonon-vlc-0.7.2" [ebuild])
(dependency required by "media-libs/phonon-4.7.2[vlc]" [ebuild])
(chroot) sysresccd / #
|
|
|
| Back to top |
|
|
P1neapple
n00b
Joined: 18 Jul 2014
Posts: 35
|
| Posted: Wed Jan 28, 2015 4:33 am Post subject: |
|
|
I got the same error mate, but it is really easy to fix.
The important lines are:
| Code: | The following REQUIRED_USE flag constraints are unsatisfied:
xml? ( extraengine ) |
That means if the "xml" USE flag is set, the "extraengine" USE flag must be set.
The following command should get rid of the error message. It simply enable the "extraengine" USE flag for mariadb:
| Code: | | echo "dev-db/mariadb extraengine" >> /etc/portage/package.use |
Also, I don't believe you should run an update before you finished your whole install (and rebooted into Gentoo) (you still seem to be in systemrescuecd)
Disclaimer: I don't use systemd. The above fix will fix the issue you are having with emerge at the moment, but I can't help you with systemd specifics.
_________________
Gentoo currently running in Virtualbox, hoping to switch to real hardware soon... |
|
| Back to top |
|
|
mreff555
Apprentice
Joined: 10 Mar 2011
Posts: 231
Location: Philadelphia
|
| Posted: Thu Jan 29, 2015 1:33 am Post subject: |
|
|
Thats exactly what it was!! Thanks. I never understood that syntax.
As far as the point at which I install systemd, I'm not exactly sure either. It seems it would be better to do before booting, but I could be wrong.
I'm pretty sure there isn't a problem with building things while still running on the recovery disk. If you chroot into a system vs booting the system the only differences are the kernel and the way you got there. The only problem I could see is if you try to install something that uses kernel info for the build such as nvidia modules which require the kernel headers.I generally build firmware and bootstrap the system with /usr/portage/scripts/bootstrap.sh before booting into the system. |
|
| Back to top |
|
|
|
Installing Gentoo
