caballist

The libaccounts-glib-1.23 package is failing to emerge due to being compiled with "treat warnings as errors" and glib-2.62.2 having deprecated the function 'g_type_class_add_private' that is in use (there is a glib deprecation macro causes a compilation warning to be emitted if the function is referenced). The function 'g_type_class_add_private' has been deprecated since glib-2.58. glib-2.58 is about a year old now and libaccounts-glib-1.23 is around 3 years old. On the assumption that I'm not the only person trying to run kde, I'm trying to understand how others could have compiled this package successfully without having to alter the build process to turn off the "-Werror" compilation flag? I'm currently investigating altering the CFLAGS variable through /etc/portage/package.env to remove "-Werror" from the compilation. it doesn't appear possible to turn off "-Werror" via CFLAGS

Steam flatpak installation and FAQ links. Change the apt commands to emerge equivalents and make sure you do the "flatpak update" mentioned in the first FAQ answer. https://www.omgubuntu.co.uk/2017/06/steam-now-available-flatpak https://github.com/flathub/com.valvesoftware.Steam/wiki/Frequently-asked-questions KDE setup... https://www.funtoo.org/KDE_Plasma_5 logind above should have read 'elogind'. I seem to remember there being 2 plasma 5 mix-ins to choose from - swapping between the 2 had no effect at all with regards to altering emerge'd packages, so choose whichever. good luck

Hi John, You don't seem to be getting any traction from anyone else so I thought I'd try to give you some pointers. I was in pretty much the same boat as you until a month ago - though I have previously trial installed gentoo/funtoo a couple of times since the 2000's Dual booting: I haven't had much luck with the automated boot update being able to chainload windows on my desktop (separate boot disks for window/funtoo) or my laptop (single disk). I haven't had time to investigate what's going wrong so I'm using the EFI BIOS to select the required boot rather than grub. If you want to play games on your 1060, use the proprietary drivers. This requirement appears to be linked to how you can run steam - see below. make.conf hasn't been deprecated (or I missed that memo). I still use it for global USE flags, MAKEOPTS, LINGUAS, L10N, VIDEO_CARDS... emerge does a good job of auto updating the /etc/portage/package.* files for package specific stuff (you need to do 'etc-update' and re-run emerge though). KDE is my old favourite DE and I'm using it again now. When trying to setup your session manager use sddm and logind - I went down a route that didn't appear to be working using some older docs, but the setup instructions for sddm/logind worked for me. Steam has to be run in some sort of container to get it's 32bit library support requirements met. DR is working on funtoo 1.4 which will allow steam to work in an LXD container, but for now there are instructions on the net for running steam from a flatpak container (I can't remember which container). Worked first time for me using X11, nvidia - just remember to look for some update instructions which have to be run within the container to get the nvidia drivers into it. It takes a little while for steam to startup but once running it's fine. Apparently the drivers inside and outside the container must match. I'll try to find the specific links to the instructions I used for some of the above when I get time at work. One other thing... I keep coming across docs (possibly just the one document multiple times) telling me to do an 'emerge sync' to update package lists (needless to say I cannot find it now I want to). You need to be doing 'ego sync' to update packages.

I've got the same problem. It's being caused by the softlink in /var/tmp/portage/dev-libs/libxml2-2.9.5 to the files directory which should exist at /var/git/meta-repo/kits/core-kit/dev-libs/libxml2/files. /var/git/meta-repo/kits/core-kit/dev-libs/libxml2/files does not exist.

ah ha! the damned obvious fix I should have thought of myself :) thnx cardinal

Trying to re-emerge procps and it's trying to download the following patch file: procps-3.3.11-remove_Unix98_output_limits.patch This file is apparently recorded as having a size of 7582 bytes in portage, but the file being downloaded is 8390 bytes. Comparing the original file from a gentoo mirror site (from 2015) it looks like the file currently being downloaded has had some lines of commentary added and this has not been reflected elsewhere. Can this be fixed up - either by reverting to the original patch file portage is expecting or by updating the portage indexes to expect the new file ?