Alec Ten Harmsel wrote:
> On Sat, Jun 15, 2019, at 14:19, Walter Dnes wrote:
>> On Thu, Jun 13, 2019 at 05:15:41PM +0300, Alexey Eschenko wrote
>>> Thank you. Didn't think about that. Don't know why though. My
>>> MAKEOPTS was "-j32". Looks like that was too many for package like
>>> qtwebengine.
On Sat, Jun 15, 2019, at 14:19, Walter Dnes wrote:
> On Thu, Jun 13, 2019 at 05:15:41PM +0300, Alexey Eschenko wrote
> > Thank you. Didn't think about that. Don't know why though. My
> > MAKEOPTS was "-j32". Looks like that was too many for package like
> > qtwebengine. Solved the problem with
On Thu, Jun 13, 2019 at 05:15:41PM +0300, Alexey Eschenko wrote
> Thank you. Didn't think about that. Don't know why though. My
> MAKEOPTS was "-j32". Looks like that was too many for package like
> qtwebengine. Solved the problem with creating specific environment
> for qtwebengine and setting it
>
> 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
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
Neil Bothwick wrote:
> On Thu, 13 Jun 2019 12:59:18 -0500, Dale wrote:
>
>> Neil Bothwick wrote:
>>> You can set that in package.env too, I do this for Chromium:
>>>
>>> % cat /etc/portage/package.env/chromium
>>> www-client/chromium alert-done.conf disk-tmpdir.conf j2.conf
>>>
>>> % cat
On Thu, 13 Jun 2019 12:59:18 -0500, Dale wrote:
> Neil Bothwick wrote:
> > You can set that in package.env too, I do this for Chromium:
> >
> > % cat /etc/portage/package.env/chromium
> > www-client/chromium alert-done.conf disk-tmpdir.conf j2.conf
> >
> > % cat /etc/portage/env/j2.conf
> >
Neil Bothwick wrote:
> On Thu, 13 Jun 2019 14:48:04 +0300, 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
On Thu, 13 Jun 2019 14:48:04 +0300, 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
On Thursday, 13 June 2019 12:59:41 BST Adam Carter wrote:
> > You can use more swap (files) before buying more RAM.
>
> I have been doing this too. It only get used during the big builds.
>
> To create a 32G swap file and enable it (OP can do this now as the build
> runs, to keep OOM away)
> #
Thank you. Didn't think about that. Don't know why though.My MAKEOPTS was "-j32". Looks like that was too many for package like qtwebengine.Solved the problem with creating specific environment for qtwebengine and setting it up in /etc/portage/package.env/It was vry long build process but this
>
> You can use more swap (files) before buying more RAM.
>
>
I have been doing this too. It only get used during the big builds.
To create a 32G swap file and enable it (OP can do this now as the build
runs, to keep OOM away)
# fallocate -l 32G && chmod 600 && mkswap
&& swapon
use 'watch
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 this package.Right now I'm trying separate build environment with
It's the first time when I encountered a problem like this on my
system and now I'm thinking how to deal with it. Has anyone dealt with
this? Is there any solutions other than buying more RAM (I don't need
more RAM for my work/entertainment right now)?
Thanks in advance.
You can use more
On Thu, 13 Jun 2019 13:19:24 +0300, Alexey Eschenko wrote:
> For some time I have problems with dev-qt/qtwebengine (at least 5.12.3)
> build. As far as I can see it fails to build due to memory exhaustion.
> Although I have 32 GB of RAM (at least 20 of them is almost always
> free) looks like
>
> I can't really help with the problem, but I've built the same package
> recently with just 4GB of RAM. (It takes a long time.) So most likely
> it's something in your portage settings that's causing this.
>
> - Lasse
Agreed. I’ve built it recently on 16GB of RAM. My MAKEOPTS is -j13 -l5 to
Alexey Eschenko writes:
> Hi.
>
> For some time I have problems with dev-qt/qtwebengine (at least 5.12.3)
> build. As far as I can see it fails to build due to memory exhaustion.
> Although I have 32 GB of RAM (at least 20 of them is almost always free)
> looks like it's not enough. It's
Alexey,
you can check /etc/portage/make.conf and see if there is a
MAKEOPTS="-j8" or similar variable. If not, add it and make the number
of jobs small, like "-j2". I have a similar problem when I build
sys-devel/binutils; it is a huge memory hog.
- Matthew
Hi.For some time I have problems with dev-qt/qtwebengine (at least 5.12.3) build. As far as I can see it fails to build due to memory exhaustion. Although I have 32 GB of RAM (at least 20 of them is almost always free) looks like it's not enough. It's strange because I have no problems with
19 matches
Mail list logo
