Re: [gentoo-user] Profile 17.1 change errors, who's bug is it?

2019-06-14 Thread Rich Freeman
On Fri, Jun 14, 2019 at 5:20 PM Corbin Bird wrote: > > Most of the info requested is attached in a zip file. Looks like it worked fine to me. Assuming the rest of your emerge completed successfully you can just remove the symlinks as instructed in the news item and you're done. -- Rich

Re: [gentoo-user] Profile 17.1 change errors, who's bug is it?

2019-06-14 Thread Corbin Bird
On 6/14/19 3:36 PM, Rich Freeman wrote: > On Fri, Jun 14, 2019 at 4:14 PM Corbin Bird wrote: >> >> Deleted those libs in /usr/lib32 and recompilied 'binutils-libs'. >> Got new libs in /usr/lib AND --> /usr/lib32. > > Is it actually installing these in lib32, or are you just seeing them > via the

Re: [gentoo-user] Profile 17.1 change errors, who's bug is it?

2019-06-14 Thread Rich Freeman
On Fri, Jun 14, 2019 at 4:14 PM Corbin Bird wrote: > > Deleted those libs in /usr/lib32 and recompilied 'binutils-libs'. > Got new libs in /usr/lib AND --> /usr/lib32. Is it actually installing these in lib32, or are you just seeing them via the compatibility symlink? The emerge log would tell

[gentoo-user] Profile 17.1 change errors, who's bug is it?

2019-06-14 Thread Corbin Bird
Who's bug is this error? Remember the instructions : ( Gentoo news item ) - emerge -1v /lib32 /usr/lib32 - Every time that command was run it would recompile 'sys-devel/binutils'. Why? It was finding 'libiberty, liboppcodes, libbfd' from 'sys-libs/binutils-libs' in /usr/lib32. Deleted

[gentoo-user] Kernel 4.19.50 constant kernel hard locks / solved

2019-06-14 Thread Corbin Bird
Disclosure : 1 : The CPU is a AMD FX-9590 ( Fam15h ) 2 : Kernel command line parameter "eagerfpu=on" is being used. This kernel option was causing constant kernel hard locks. - General setup --> [ ] CPU isolation. - Anything that accessed the FPU would cause the CPU's ( SMP ) to "loose

Re: [gentoo-user] Not enough RAM for dev-qt/qtwebengine build

2019-06-14 Thread Adam Carter
> > More swap will help, but the basic problem here is the HUGE number of jobs > specified. If each job eats say up to 2G when it gets going, then -j32 > will > require >64G RAM to keep running without thrashing the swap device, or > running > OOM. > Yes agree. If the swapfile is on an SSD then

Re: [gentoo-user] Not enough RAM for dev-qt/qtwebengine build

2019-06-14 Thread J. Roeleveld
On June 13, 2019 11:48:04 AM UTC, Alexey Eschenko wrote: >That was my first move. Unfortunately it didn't help. > >But in the first answer in this thread I saw a good idea about >decreasing number of parallel build threads. > >I have MAKEOPTS="-j32" and it's probably the cause of my problem with