9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jim.robinson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 9atom - odd error during build phase
Date: Sun, 30 Oct 2016 03:21:38 +0000	[thread overview]
Message-ID: <CAPd04b41LirM8C58Kyp6k6+SqzBZKWmrhW475m=Q+c1MsFcZtA@mail.gmail.com> (raw)

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

Hi folks,

I've put together the parts for the CPU unit that I want to
use as a fileserver.  I haven't gotten the parts for the actual
disk array yet, but the machine got a local SSD in it and
I figured that would be good enough to at least install
a standalone system on.

This is on a Supermicro X7SPA-H-D525 (so an Intel Atom
D525 CPU). I booted this system using the 9termd kernel,
the amd64 choice, since the Intel Atom D525 has a
64-bit instruction set.

I booted the 9atom USB image, and worked my way through
the install procedure.  On the phase for building the amd64
binaries I see it gets to the point of trying to build a binary
for win and it is failing:

6l -o 6.out fs.6 main.6 pipe.6 util.6 win.6 /amd64/lib/lib9p.a
??none??: fs.6: opcode out of range 0
        probably not a .6 file
mk: 6l -o ... : exit status=rc 7719: 6l 7721: error
mk: @{cd bin/source; mk ... : exit status=rc 7693: rc 7695: mk 7697: error
mk: date for (i ... : exit status=rc 631: rc 7690: mk 7692: error

and then throws up the halt prompt.

I halted the system and could see that I was able to boot off
the SSD fossil partition.  It let me log in (as glenda).  I went
to /sys/src and ran mk to see if it threw out the same error
and it did not, it linked 6.out properly and proceeded building
the rest of the source tree.

Anyone know what might have caused a failure like that?
My uneducated guess would be that it maybe hit a problem
writing data on the usb stick I was booting off of (it appeared
to me that it was using the usb stick instead of the filesystem
created during the install to run the compile).

Jim

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

                 reply	other threads:[~2016-10-30  3:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPd04b41LirM8C58Kyp6k6+SqzBZKWmrhW475m=Q+c1MsFcZtA@mail.gmail.com' \
    --to=jim.robinson@gmail.com \
    --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).