valerievonck Posted November 16, 2017 Report Share Posted November 16, 2017 @Oleg Vinichenko Please find the results of my tests under a Virtual Box machine: - First I had to add "amd64" to KEYWORD variable in the ebuild under: /var/git/meta-repo/core-kit/ - Then I had to expand the virtual harddisk, so that I had 20G free (from 32G to 60G) (ubuntu live cd) - Then I had to do a emerge -av ">=debian-sources-4.13.10-1" because with an ego sync && emerge -avuND world it dit not show up in the package tree, when I searched for it. It compiled without a problem, and after (manually) adapting the /boot/grub/grub.cfg, replacing 4.8.15-1 with the correct version, the Virtual Machine booted up correctly Also, KDE Plasma with virtual box guest additions booted up correctly. Kind regards, Valerie Link to comment Share on other sites More sharing options...
Oleg Vinichenko Posted November 16, 2017 Report Share Posted November 16, 2017 thank you. yes, the ebuild has no keywords, so adding them is step prior to emerge. Yes, due to many modules enabled by default, during compilation disk space consuming picks around 18Gb, so 20Gb is set so that there is plenty of space. Link to comment Share on other sites More sharing options...
Recommended Posts