maratbn

Sure, the output is: lrwxrwxrwx 1 root root 18 Oct 7 23:01 /etc/runlevels/boot/binfmt -> /etc/init.d/binfmt lrwxrwxrwx 1 root root 20 Oct 7 23:01 /etc/runlevels/boot/bootmisc -> /etc/init.d/bootmisc lrwxrwxrwx 1 root root 16 Oct 7 23:01 /etc/runlevels/boot/fsck -> /etc/init.d/fsck lrwxrwxrwx 1 root root 20 Oct 7 23:01 /etc/runlevels/boot/hostname -> /etc/init.d/hostname lrwxrwxrwx 1 root root 19 Oct 7 23:01 /etc/runlevels/boot/hwclock -> /etc/init.d/hwclock lrwxrwxrwx 1 root root 19 Oct 7 23:01 /etc/runlevels/boot/keymaps -> /etc/init.d/keymaps lrwxrwxrwx 1 root roo

So I have 'x11-misc/lightdm' version 1.24.0 installed, and configured to start automatically, which it does. Before logging in, I click on the configuration icon in the upper right, and change 'Xsession' to 'Xfce Session', but when I do login, I still get the Xsession. Here are my lightdm log files when I login if this is helpful: [+514.61s] DEBUG: Continue authentication ==> /var/log/lightdm/seat0-greeter.log <== (lightdm-gtk-greeter:3173): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar) (ligh

OK, thanks Oleg, works now after 'ego sync'. I see your commit: https://github.com/funtoo/kit-fixups/commit/94e0ae64d79efd6ca03a849fe0426c53d37c57d1#diff-54f4a5f008b420d3daba1a5dbd40408a I take it that file 'funtoo-cautionary' is something like a patch file for the original 'package.mask' from Gentoo, and the minus sign means that that default Gentoo mask entry is getting removed? Thanks, Marat

You can see the full output of my 'emerge xorg-x11' command, which is what emitted that unmask message for me, in my first post above. I did not use any additional command line arguments for that command. Would you like me to run it again with '-v' or anything else?

Hmmm, I just ran this command, but it did not produce any output, as I do not have the token 'xorg-server' in any file under my '/etc/portage'... And if I just do 'grep -r xorg /etc/portage', I only get: /etc/portage/make.profile/parent:xorg-kit:funtoo/kits/python-kit/3.4-prime Thanks, Marat

OK, I was able to post my post now, thanks a lot Daniel.

I'm following the instructions at https://www.funtoo.org/X_Window_System When I try to 'emerge xorg-x11', I get the following Portage output: Calculating dependencies... done! [ebuild N ] sys-libs/mtdev-1.1.5 USE="-static-libs" [ebuild N ] media-fonts/font-alias-1.0.3-r1 [ebuild N ] x11-misc/xbitmaps-1.1.1 [ebuild N ] x11-proto/xf86dgaproto-2.1-r2 ABI_X86="(64) -32 (-x32)" [ebuild N ] x11-proto/fontsproto-2.1.3 USE="-doc" [ebuild N ] x11-apps/xcursorgen-1.0.6 [ebuild N ] dev-libs/libevdev-1.5.4 USE="-static-libs" ABI_X86="(64) -32 (-x32)"

I tried to post into the Portage Help forum the output of an 'emerge' that contains a Gentoo contributor's email next to a package they masked, but when I clicked 'Submit Topic' I got the error "*** Forbidden. Contains contacts. Message seems to be spam. ***" I think this is due to the new spam prevention technology discussed here --

I was able to emerge chromium successfully with gcc 5.4.0 Thank you everybody!

Ah, so I only need gcc version 5.4.0 not > 5.4.0 And so the 5.4.0 is currently not masked? I think I'll eselect 5.4 and try it again. Thanks!

OK, not "not supported", just requires unmasking. I looked at the replies more closely, and see that bug https://bugs.funtoo.org/browse/FL-4235 was filed on this issue, and gcc 5.4 which can compile that version of chromium can now be selected with 'eselect' without having to unmask it.

OK, understand that the latest chromium package is not compiling because the latest supported version of gcc does not support compiling it. But then, if that chromium package cannot be compiled, why is it not masked so that the previous version that could be compiled would be used instead? Is it not masked for the users that use clang instead of gcc? I assume there is no way to select which compiler to use on a per-package basis? Thanks, Marat

I'm getting a compilation error when trying to emerge 'www-client/chromium-62.0.3202.18::net-kit'. Here's the compilation error: FAILED: obj/services/device/generic_sensor/generic_sensor/platform_sensor_reader_linux.o x86_64-pc-linux-gnu-g++ -MMD -MF obj/services/device/generic_sensor/generic_sensor/platform_sensor_reader_linux.o.d -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DDISABLE_NACL -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LA