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 decreased job count value and it looks promissing. I'll leave the message with results in the reply to that message. �� 13.06.2019, 14:13, "Neil Bothwick" <neil@××××××××××.uk>:
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 it's not enough. It's strange because I have no
��problems with Firefox/Chromium/Libreoffice builds.
Do you have $PORTAGE_TMPDIR on a tmpfs filesystem? I had a similar
problem, on a slightly less well-endowed system, and had to use
portage.env to instruct that ebuild, as well as chromium and libreoffice,
to use a directory on my SSD for PORTAGE_TMPDIR.
% cat /etc/portage/package.env/qt
dev-qt/qtwebengine disk-tmpdir.conf
% cat /etc/portage/env/disk-tmpdir.conf
PORTAGE_TMPDIR="/mnt/scratch"
��
--
Neil Bothwick
Assassins do it from behind.
Archives