From: Leo Famulari <leo@famulari.name>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 32768@debbugs.gnu.org
Subject: [bug#32768] [PATCH] gnu: go-1.11: Add New Version
Date: Wed, 19 Sep 2018 17:20:32 -0400 [thread overview]
Message-ID: <20180919212032.GA6893@jasmine.lan> (raw)
In-Reply-To: <877ejinqph.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
On Tue, Sep 18, 2018 at 09:52:58PM -0500, Katherine Cox-Buday wrote:
> +(define-public go-1.11
Thanks!
I tested that some basic packages build within the go-build-system using
Go 1.11 (several need to be updated to support Go 1.11, however).
> + ;; A side affect of these test scripts is testing
> + ;; cgo. Attempts at using cgo flags and
> + ;; directives with these scripts as specified
> + ;; here (https://golang.org/cmd/cgo/) have not
> + ;; worked. The tests continue to state that they
> + ;; can not find crt1.o despite being present.
> + "cmd/go/testdata/script/list_compiled_imports.txt"
> + "cmd/go/testdata/script/mod_case_cgo.txt"
> + ;; https://github.com/golang/go/issues/24884
> + "os/user/user_test.go"))
Okay, we can punt on this for now.
> + (replace 'set-bootstrap-variables
> + (lambda* (#:key outputs inputs #:allow-other-keys)
> + ;; Tell the build system where to find the bootstrap Go.
> + (let ((go (assoc-ref inputs "go")))
> + (setenv "GOROOT_BOOTSTRAP" go)
> + (setenv "GOGC" "400")
> + ;; Go 1.10 tries to write to $HOME in a test
> + (setenv "HOME" "/tmp")
> + #t)))))))))
This phase is identical to the one that would be inherited from Go 1.10,
right?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-19 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 2:52 [bug#32768] [PATCH] gnu: go-1.11: Add New Version Katherine Cox-Buday
2018-09-19 21:20 ` Leo Famulari [this message]
2018-09-21 14:58 ` Katherine Cox-Buday
2018-09-22 18:44 ` bug#32768: " Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180919212032.GA6893@jasmine.lan \
--to=leo@famulari.name \
--cc=32768@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).