Jump to content


  • Content Count

  • Joined

  • Last visited

  1. @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
  2. Thank you @Oleg Vinichenko, kind regards, Valerie
  3. jhan, Indeed, when doing eix -s mesa, only these two packages are shown, :s, but it is not available (anymore)... Is anyone experiencing this as well ? (fresh installation)?
  4. Yesterday, I successfully installed Funtoo on ZFS in a virtual box. Then I added the desktop flavor and added my mix-ins. I did an emerge -avuND world, to get all the packages, but when emerge wanted to pull in mesa, the scripts says: directory is no longer available. On my other Funtoo virtual box, this package is installed But in my Gentoo virtual box, the package is on version 17.0.6? Can anyone help me please? Do I have to unmask this package in /etc/portage/package.use? (>=media-libs/mesa-13.0.1 tilde amd64)? Or do I have to create a bug? Thank you, Kin
  5. I got the same problem, but with a ego syncand a emerge -avuND @worldit started pulling in the updates. Edit: in my make.conf there are no longer PYTHON_TARGET nor PYTHON_SINGLE_TARGET Edit 2: on my other vbox, I had to pull in libpcre2 & xmlsec ebuilds to start the world update... (and do an etc-update) Kind regards, Valerie
  6. Ok :) My misunderstanding, I thought you meant, leave the make.conf empty... :huh: My mistake, Thank you for the swift reply!
  7. Just a question, not wanting to start a discussion nor a flamewar. I have been a long time Gentoo user, and I am used to do everything to do with : /etc/portage/make.conf, I know that people are going to say, Funtoo != Gentoo, I could not agree more, it is fast & lean, just how an OS must be. A staff member said: I respect his opinion, but why is Funtoo taken this approach (to move away from make.conf) or why I am not getting it, I am trying to understand and learn... If I do not set my makeopts, will Funtoo be able to determine my (virtual) cpu's? Just wondering...
  8. Removed the lines from make.conf, run epro update, and emerge -avuND @world It is pulling in the updates, Thank you!!
  9. @Oleg Vinichenko, Thank you for your insight, I will try this when building a new VBox Machine. emerge -s ego | more yielded ego 1.1.3-r5 Marking this topic as [solved] Thank you! Kind regards, Valerie
  10. Hello everyone, Since a couple of months I am using Funtoo in Virtual Box, up until now, I have got no problems installing Funtoo in following configurations: - Base install - KDE - Base install + ZFS Past weekend I did follow the instructions for using the new ego system, mentioned at http://www.funtoo.org/News:Kits_Are_Go_(And_Ego_Needs_a_Manual_Bump) , also I have read on the forum to do an additional chown -R portage:portage. I will post my make.conf CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j5" ACCEPT_LICENSE="* @EULA" CHOST="x86_64-pc-linux-gnu" USE="alsa g
  • Create New...