Re: [gentoo-user] Stack Clash and -fstack-check

2017-06-19 Thread Rasmus Thomsen
Hi, -fstack-check seems to be kind of broken on gcc right now: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68065 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66479 it's a no-op for clang IIRC Regards, Rasmus Original Message On 20 Jun 2017, 07:50, Adam Carter wrote: Given; h

Re: [gentoo-user] Radeon driver not happy

2017-06-19 Thread Adam Carter
On Sun, Jun 18, 2017 at 2:00 AM, Mick wrote: > Since the last radeon/xorg/mesa update things have been rather ropey on two > different boxen If you're changed kernels since you last rebuilt xorg-server (shown in the top of the Xorg.0.log file) then there's a very small chance rebuilding it will

[gentoo-user] Stack Clash and -fstack-check

2017-06-19 Thread Adam Carter
Given; https://www.theregister.co.uk/2017/06/20/stack_clash_linux_local_root_holes/ would it make sense to add -fstack-check to CFLAGS and rebuild everything, starting with packages that install suid root binary(ies)?

Re: [gentoo-user] glibc-2.24-r2 failed (install phase)

2017-06-19 Thread tuxic
On 06/19 11:55, Alexander Kapshuk wrote: > On Mon, Jun 19, 2017 at 6:21 AM, wrote: > > On 06/15 05:56, tu...@posteo.de wrote: > >> Hi, > >> > >> While updateing glibc-2.24-r2 failed to install. > >> > >> These are the last few lines of that process: > >> > >> > >> al/execinfo.c.texi > >> /v

Re: [gentoo-user] glibc-2.24-r2 failed (install phase)

2017-06-19 Thread Alexander Kapshuk
On Mon, Jun 19, 2017 at 6:21 AM, wrote: > On 06/15 05:56, tu...@posteo.de wrote: >> Hi, >> >> While updateing glibc-2.24-r2 failed to install. >> >> These are the last few lines of that process: >> >> >> al/execinfo.c.texi >> /var/tmp/portage/sys-libs/glibc-2.24-r2/work/build-amd64-x86_64-p

Re: [gentoo-user] Re: KDE 5 MTP failure

2017-06-19 Thread Peter Humphrey
On Sunday 18 Jun 2017 20:48:53 Walter Dnes wrote: > On Mon, Jun 19, 2017 at 01:19:58AM +0100, Peter Humphrey wrote > > > On Sunday 18 Jun 2017 14:11:02 Walter Dnes wrote: > > > An extra bit of debugging... > > > > > > * switch to message log console (tty12) with {CTRL}{ALT}{F12} > > > > > > * at