From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] amd64 bootstrap file fo go1.16.3
Date: Tue, 20 Apr 2021 08:02:57 +0900 [thread overview]
Message-ID: <147A6A86F6381EFA577F65EE506E5D6C@hera.eonet.ne.jp> (raw)
In-Reply-To: <D5BF6ADDF24EE78B98B0F9816F617FC5@hera.eonet.ne.jp>
Ok, I write the fact which happened to make go1.16.3-plan9-amd64-bootstrap
from go1.16.3-plan9-amd64-bootstrap.tbz:
-----from here----
I made first go1.16.3-plan9-amd64-bootstrap.tar on this Plan9.
cpu% cat go1.16.3-plan9-amd64-bootstrap.tar|{cd /sys/lib/go; tar xT}
tar: // Copyright 2018 The Go Authors. All rights reserved.
// Use of this source code is governed by a B: ENSE file.
// Package analysisutil defines various helper functions
// used by two or more packages beneath go/analysis.
package analysisutil
import (
"bytes"
"go/ast"
"go/printer"
"go/token"
"go/types"
"io/ioutil"
)
// Format returns a string representation of the expression.
func Format(fset *token.FileSet, x ast.Expr) string {
var b bytes.Buffer
printer.Fprint(&b, fset, x)
return b.String()
}
// HasSideEffects reports whether evaluation of e has side effects.
func HasSideEffects(info *types.Info, e ast.Expr) bool {
safe := true
ast.Inspect(e, func(node ast.Node) bool {
switch n := node.(type) {
case *ast.CallExpr:
typVal := info.Types[n.Fun]
switch {
case typVal.IsType():
// Type conversion, which is safe.
case typVal.IsBuiltin():
// Builtin func, conservatively assumed to not
// be safe for now.
safe = false
return false
default:
// A non-builtin func or method call.
// Conservatively assume that all of them have
// side effects for now.
safe = false
return false
}
case *ast.UnaryExpr:
if n.Op == token.ARROW {
safe = false
return false
}
}
return true
})
return !safe
}
// Unparen returns e with any enclosing parentheses stripped.
func Unparen(e ast.Expr) ast.Expr {
for {
p, ok := e.(*ast.ParenExpr)
if !ok {
return e
}
e = p.X
}
}
// ReadFile reads a �: non-numeric checksum in header
tar: bad archive header checksum in archive: name // Copyright 2018 The Go Authors. All rights reserved.
// Use of this source code is governed by a B...; expected 037777777777 got 0125506
cpu%
cpu% lc /sys/lib/go/go-plan9-amd64-bootstrap
bin pkg src test
--------to here------
I, then, make go-plan9-amd64-bootstrap file tree on Linux, and copy it to /sys/lib/go.
From the procedures above, I thought go-plan9-amd64-bootstrap.tbz was built on a
certain system other than Plan9.
Kenji
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T75ee4ccd407669dd-Mf588e3fb610031e0f0ce251f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-04-19 23:03 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 [this message]
2021-04-20 7:24 ` David du Colombier
2021-04-20 23:03 ` kokamoto
2021-04-27 6:00 ` kokamoto
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=147A6A86F6381EFA577F65EE506E5D6C@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).