From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,URIBL_RED autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 27944 invoked from network); 9 Jan 2021 23:50:50 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 9 Jan 2021 23:50:50 -0000 Received: from cmo-0002.xspmail.jp ([202.238.198.172]) by 1ess; Sat Jan 9 18:24:17 -0500 2021 Received: from cmr-0000.xspmail.jp ([202.238.198.117]) by cmo with ESMTP id yNYCkJkjiUfQ6yNaekk4Ga; Sun, 10 Jan 2021 08:24:12 +0900 Received: from ci5dell.jitaku.localdomain ([180.147.122.76]) by cmr with ESMTPA id yNadkCLwlVarDyNadkcFRb; Sun, 10 Jan 2021 08:24:12 +0900 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hera.eonet.ne.jp; s=x01; t=1610234652; i=kokamoto@hera.eonet.ne.jp; bh=tcW/fgo9knnskl/N/lIsLJLcSRd/PCqj4i86Hp6owY8=; h=To:Subject:Date:From:In-Reply-To; b=CuDDpbXdGk7UzCEd8rreDBt9D+qgI+nAra5nImfd7JMLrfDYWImWzAGMVuX0q87n7 uIWs1CmasFQnJ/e4kDNWdB68U+T6i/9xJKlHdq3CxUU3KmKLQldVfpHSg5vFgOi1qc 4q2zjDD/z3+ONzLWu7QpycoOBnwEJLjX24jJX0StOnE/pRCvar5ZTQ9rwnYIIUVQjZ GFij5em85FeudHW0I3lEFhcjYOT4na7rKdp8FAqha3BMOkyI8Ci3KdAZUiW59Myclb K4RJaq7vKl81tp3R8K3H6z6NQ2mqGxZHLnR8Q/n1jw3CleWuPs6M9t+14HJAjI0heO 9SXf4w574pe0A== Message-ID: <15FCAE441BA9B51FD261B7CDD1696A7E@hera.eonet.ne.jp> To: 9front@9front.org Date: Sun, 10 Jan 2021 08:24:09 +0900 From: kokamoto@hera.eonet.ne.jp In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-qtclzojwvigbddnkkleuqcwxky" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: content-addressed managed framework Subject: Re: [9front] Patch to update Go to 1.14.6 (and ca-certificates while here) Reply-To: 9front@9front.org Precedence: bulk This is a multi-part message in MIME format. --upas-qtclzojwvigbddnkkleuqcwxky Content-Disposition: inline Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit I tried both of 9legacy's bootstrap and that for 9front, and got success for both without any patches. Your method looks difficult to me.☺ 1) follow the method by kylejnusbaum@gmail.com 2) put 1.14.1 bootstrap files to /sys/lib/go/go-plan9-amd64-bootstrap, and go-plan9-1.15.6 to /sys/lib/go/amd64-1.15.6 (which is written by sl's FAQ) set GOROOT_BOOTSTRAP=/sys/lib/go/go-plan9-amd64-bootstrap, GOROOT=/sys/lib/go/amd64-1.15.6, GOPAS=$home/Go then, cd to /sys/lib/go/amd64-1.15.6, and ./make.rc By the way, I'm looking your opossum source now, which looks like very compact, because many are hidden under the $home/Go/git.hub etc... Go is beautiful to me. Kenji --upas-qtclzojwvigbddnkkleuqcwxky Content-Type: message/rfc822 Content-Disposition: inline Return-Path: 9front-bounces@1ess.inri.net Received: from cmi-0004.m.xspmail.jp (LHLO cmi-0004.xspmail.jp) (100.120.21.5) by zmbs-0041.m.xspmail.jp with LMTP; Sun, 10 Jan 2021 04:17:29 +0900 (JST) Received: from 1ess.inri.net ([216.126.196.35]) by cmi with ESMTP id yJjqkpeYvRn6dyJjrk2Ub3; Sun, 10 Jan 2021 04:17:28 +0900 X-Country-Code: US Authentication-Results: cmi-0004.xspmail.jp; dkim=fail (signature verification failed) header.d=protonmail.com header.b=hR8pksqG; dmarc=fail header.from=protonmail.com; x-token-a=none; x-token-b=fail Received-SPF: PASS identity=mailfrom; envelope-from="9front-bounces@1ess.inri.net" Received: from mail2.protonmail.ch ([185.70.40.22]) by 1ess; Sat Jan 9 14:02:52 -0500 2021 Date: Sat, 09 Jan 2021 19:02:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1610218968; bh=GrI6IAKnTEd93G6WTSKxv3m+zuHnYlVUKxRoJljPeT8=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From; b=hR8pksqGCqkiD1hpuBhi1I4PJTsEHYIWz+H+JenSvQjk3QAPhmzbfkO2CVgyM5nr7 FUjFuwUzrm7a6jPrv0Rz4UvHurh1p57pi2/FY/IRKSDN5yXUmoQlSEI2Cumre8swfy cou10yMaIHMFBfoT0p5AbbTRbExoYWbclHl7NWho= To: "9front@9front.org" <9front@9front.org> From: Philip Silva Message-ID: In-Reply-To: <1F9106FA44696AEEF73230E0CBFD8B15@gmail.com> References: <1F9106FA44696AEEF73230E0CBFD8B15@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: high-performance information ACPI over SQL realtime hosting Subject: Re: [9front] Patch to update Go to 1.14.6 (and ca-certificates while here) Reply-To: 9front@9front.org Precedence: bulk For me bootstrapping also worked with the 9legacy Go1.14.1 when doing this = on the amd64 iso of 9front - although I had problems in the beginning, mayb= e because of the env vars. So in the end I've been putting the bootstrapped= Go into /usr/glenda/go-plan9-amd64-bootstrap, set the /usr/glenda/env/GORO= OT_BOOTSTRAP (bind -a /usr/glenda/env /env) permanently to /usr/glenda/go-p= lan9-amd64-bootstrap with GOROOT - and I believe also GOPROXY - being unset= . Also I've then set: bind -a $home/go-plan9-amd64-bootstrap/bin /bin Afterwards: cd $home/go1.15.6/src and all.rc. Still need to try the patch t= hough. By the way, there are also scripts for that, like here: http://shithub.us/g= it/fulton/rc-scripts/HEAD/install/install-go.rc/f.html Greetings, Philip =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Am Mittwoch, 6. Januar 2021 21:45 schrieb : > I am using my own amd64 bootstrap tarball for Go built from 1.15.3. > (http://9project.net/go-plan9-amd64-bootstrap.tar.gz) > > Using this, I am able to bootstrap Go on 9front. > > As a side note, I used to have trouble using the bootstrap package to > cross-compile (i.e. using my amd64 bootstrap tarball on amd64 to > compile plan9 386) so I instead built for plan9 amd64 first, and then > use that as a bootstrap for any other arches I want, like this: > > 1. go-plan9-amd64-bootstrap.tar.gz to bootstrap Plan9 Go amd64 > 2. Plan9 Go amd64 to bootstrap other arches (386, arm) > > I just tried it again, and that doesn't seem to be an issue for me > anymore, but I thought I'd mention it. > > With the bootstrap unpacked into /sys/lib/go/amd64, my command > and output (building 1.15.6 for 386 on amd64) look like this: > > GOOS=3Dplan9 GOARCH=3D386 GOHOSTARCH=3Damd64 GOROOT_FINAL=3D/sys/lib/= go/386 GOROOT_BOOTSTRAP=3D/sys/lib/go/amd64 ./make.rc > Building Go cmd/dist using /sys/lib/go/amd64 > Building Go toolchain1 using /sys/lib/go/amd64. > Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1. > Building Go toolchain2 using go_bootstrap and Go toolchain1. > Building Go toolchain3 using go_bootstrap and Go toolchain2. > Building packages and commands for host, plan9/amd64. > Building packages and commands for target, plan9/386. > > > Installed Go for plan9/386 in /9bps/buildroot/go-1.15.6_1/build/go-go1.15= .6 > Installed commands in /9bps/buildroot/go-1.15.6_1/build/go-go1.15.6/bin > > The binaries expect /9bps/buildroot/go-1.15.6_1/build/go-go1.15.6 to be c= opied or moved to /sys/lib/go/386 --upas-qtclzojwvigbddnkkleuqcwxky--