9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] amd64 bootstrap file fo go1.16.3
Date: Tue, 27 Apr 2021 15:00:50 +0900	[thread overview]
Message-ID: <0DEAFD87F9B59FD6CEB22857C1F83225@hera.eonet.ne.jp> (raw)
In-Reply-To: <E8E9812A5AD29746E8A8D034892DDA48@hera.eonet.ne.jp>

>> I've fixed this issue a couple of days ago. The most recent archives
>> were not in ustar format. Please re-download the bootstrap.
> 
> Yes, I did it, and got the following error:
> 
> Building Go cmd/dist using /sys/lib/go/go-plan9-amd64-bootstrap
> kickpager page size 4K color -1
> iallocb: no memory 864/78293674
> out of physical memory
> 133: compile killed: out of physical memory
> kickpager page size 4K color -1
> kickpager page size 4K color -1
> go tool compile: exit status: compile 133: killed: Insufficient physical memory

This error might have occured when 6c/6l are running.
I saw same error message to compile /sys/src/cmd/gs by native amd64 terminal.
On amd64 mode 9legacy terminal
term% cd /sys/src/cmd/gs
term% make install
then got the error messages like:
kickpager page size 4k color -1
out of physical memory
mk: pcc -o...:exit status=rc 3033: pcc 3035: 6l: 6l 3036:
killed: insufficient physical memory
rc 131: mk 132: error

This error occured mk is trying to link many object to final gs.

Interestingly, this does not occur when compiling on 386 environment,
like objtype=amd64 mk install.

Then, I suspect /amd64/bin/6l has some problem.

Kenji


------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T75ee4ccd407669dd-M119a1fda009e322227594329
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-04-27  6:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18  0:28 kokamoto
2021-04-18  4:05 ` kokamoto
2021-04-18  8:36   ` Philip Silva via 9fans
2021-04-18 22:36     ` kokamoto
2021-04-19 23:02       ` kokamoto
2021-04-20  7:24         ` David du Colombier
2021-04-20 23:03           ` kokamoto
2021-04-27  6:00             ` kokamoto [this message]
2021-04-27  7:01               ` David du Colombier
2021-04-21  9:39       ` Richard Miller
2021-04-21 14:27         ` Bakul Shah
2021-04-21 15:04           ` Richard Miller
2021-04-20 23:05     ` kokamoto
2021-04-21  5:23     ` kokamoto
2021-04-21  6:56       ` David du Colombier
2021-04-21  9:20         ` kokamoto
2021-04-21  9:29           ` Richard Miller
2021-04-21 11:04             ` kokamoto
2021-04-18  9:08 ` David du Colombier
2021-04-18 10:19   ` kokamoto

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=0DEAFD87F9B59FD6CEB22857C1F83225@hera.eonet.ne.jp \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).