public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Franz Fellner <alpine.art.de@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-3.6.5 rebuild fails on new install
Date: Mon, 20 Aug 2018 08:46:22 +0300	[thread overview]
Message-ID: <CADtyuE5eEenKDhe_NnRps=b57aNXpRFSHRukknY8dSk8in0Pfg@mail.gmail.com> (raw)
In-Reply-To: <CAC=wYCHEgixuZ4wGOCiNyk8-s87=BiP-1Zk47SfLK0xdepGkWg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

Seems to be a known issue and probably fixed in gcc-7.4.0:
https://bugs.gentoo.org/662208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83317

This error is also used in the Gentoo gcc internal compiler error reporting
wiki page:
https://wiki.gentoo.org/wiki/Gcc-ICE-reporting-guide

Am Mo., 20. Aug. 2018 um 08:23 Uhr schrieb Adam Carter <
adamcarter3@gmail.com>:

>   I just tried with MAKEOPTS="-j1" and got the same failure output at
>> the same place.  I normally run with the number equal to the number of
>> cores.  On this notebook MAKEOPTS="-j2".  Are there any other
>> memory-conserving tweaks available?
>>
>
> I guess you've stopped all the non-essential services and programs.
>
> Does top or free -m confirm that you're running out of space? If so, you
> could create a temporary swap file on an existing filesystem (
> https://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/) or make a USB
> drive into some temporary swap get you through the build
>
>

[-- Attachment #2: Type: text/html, Size: 1821 bytes --]

  reply	other threads:[~2018-08-20  5:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18  0:58 [gentoo-user] python-3.6.5 rebuild fails on new install Walter Dnes
2018-08-18 19:27 ` Mike Gilbert
2018-08-19  1:56   ` Walter Dnes
2018-08-19  2:27     ` Walter Dnes
2018-08-19  7:41       ` Franz Fellner
2018-08-19  9:49     ` Mick
2018-08-19 17:18       ` Walter Dnes
2018-08-20  5:22         ` Adam Carter
2018-08-20  5:46           ` Franz Fellner [this message]
2018-08-20 15:35             ` Walter Dnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADtyuE5eEenKDhe_NnRps=b57aNXpRFSHRukknY8dSk8in0Pfg@mail.gmail.com' \
    --to=alpine.art.de@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox