Re: [gentoo-user] Boot Gentoo live iso from grub

On 02/18/18 12:25, Neil Bothwick wrote: > On Sun, 18 Feb 2018 11:10:38 -0800, Daniel Frey wrote: > >> I started moving away from Grub2 mostly because on my EFI computers it >> was booting in blind mode so you couldn't see what was going on while >> booting. > > I moved away from it on my EFI

[gentoo-user] Suboptimal emerging of python libraries with native code

I just emerged sci-libs/scipy. I was unpleasantly surprised that the job only loaded one of my cpus most of the time, resulting in a longish wait (15-20 minutes). I investigated a bit. Originally, I had this in make.conf: MAKEOPTS="-j5" Then I had a look at the ebuild. I saw that it inherits

Re: [gentoo-user] Re: Mammoth emerge ...

On Thursday, 3 May 2018 18:00:45 BST Corbin Bird wrote: > . > Chromium switched to 'clang++ v5.x' as its primary compiler. > Why? > The Chromium devs are using 'c++' features supported in gcc v8+. > . > So ... first compile run is with 'gcc' ... then Chromium is re-compiled > with 'clang++'. >

Re: [gentoo-user] Re: Mammoth emerge ...

On Thursday, 3 May 2018 17:57:20 BST Neil Bothwick wrote: > On 3 May 2018 16:41:55 BST, Grant Edwards wrote: > >On 2018-05-03, Mick wrote: > >> OK, I know my laptop is quite old, or at least Intel thinks so, but > > > >emerging > > > >>

Re: [gentoo-user] Re: Mammoth emerge ...

. Chromium switched to 'clang++ v5.x' as its primary compiler. Why? The Chromium devs are using 'c++' features supported in gcc v8+. . So ... first compile run is with 'gcc' ... then Chromium is re-compiled with 'clang++'. That is what I am seeing ( console && log wise ). 2 Compile runs ... twice

Re: [gentoo-user] Re: Mammoth emerge ...

On 3 May 2018 16:41:55 BST, Grant Edwards wrote: >On 2018-05-03, Mick wrote: > >> OK, I know my laptop is quite old, or at least Intel thinks so, but >emerging >> chromium is now taking *much* longer than it ever did: > >A while back I

Re: [gentoo-user] Re: Mammoth emerge ...

On Thursday, 3 May 2018 16:41:55 BST Grant Edwards wrote: > On 2018-05-03, Mick wrote: > > OK, I know my laptop is quite old, or at least Intel thinks so, but > > emerging > > chromium is now taking *much* longer than it ever did: > A while back I accidentally broke the

[gentoo-user] Re: Mammoth emerge ...

On 2018-05-03, Mick wrote: > OK, I know my laptop is quite old, or at least Intel thinks so, but emerging > chromium is now taking *much* longer than it ever did: A while back I accidentally broke the CPU throttling on my laptop, and it was always running at 1/4

Re: [gentoo-user] Mammoth emerge ...

On Thursday, 3 May 2018 15:58:44 BST Mick wrote: > Is there anything I can do with the existing laptop and its limited > resources to speed up chromium's emerge? All I can suggest is to build a package in a chroot on a speedier machine and transfer it to the laptop. That's how I cope with a

[gentoo-user] Mammoth emerge ...

OK, I know my laptop is quite old, or at least Intel thinks so, but emerging chromium is now taking *much* longer than it ever did: Tue Apr 24 11:55:49 2018 >>> www-client/chromium-66.0.3359.117 merge time: 1 day, 16 minutes and 28 seconds. I'm currently emerging