From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: "James A. Robinson" Date: Sun, 30 Oct 2016 03:21:38 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=94eb2c03125c7de52805400c97f2 Subject: [9fans] 9atom - odd error during build phase Topicbox-Message-UUID: a78b8470-ead9-11e9-9d60-3106f5b1d025 --94eb2c03125c7de52805400c97f2 Content-Type: text/plain; charset=UTF-8 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 --94eb2c03125c7de52805400c97f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi folks,

I've put together the par= ts for the CPU unit that I want to
use as a fileserver.=C2=A0 I h= aven't gotten the parts for the actual
disk array yet, but th= e 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,
th= e amd64 choice, since the Intel Atom D525 has a
64-bit instructio= n set.

=
I booted the 9atom USB image, and worked my way through
the install procedure.=C2=A0 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 o= ut of range 0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 probably not a .6 file<= /div>
mk: 6l -o ... : exit status=3Drc 7719: 6l 7721: error
m= k: @{cd bin/source; mk ... : exit status=3Drc 7693: rc 7695: mk 7697: error=
mk: date for (i ... : exit status=3Drc 631: rc 7690: mk 7692: er= ror

and then throws up the halt prompt.
=
I halted the system and could see that I was able to boot of= f
the SSD fossil partition.=C2=A0 It let me log in (as glenda= ).=C2=A0 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 proceede= d building
the rest of the source tree.

= Anyone know what might have caused a failure like that?
My uneduc= ated guess would be that it maybe hit a problem
writing data on t= he 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

--94eb2c03125c7de52805400c97f2--