unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Petter <petter@mykolab.ch>, Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] Go: Update to 1.7
Date: Tue, 06 Sep 2016 09:45:45 +0000	[thread overview]
Message-ID: <878tv57452.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <8f74c0ea6b1b2eb5328705f3b98cd75a@mykolab.ch>

I just started working on this in my gogs-feature guix checkout, when
Petter pointed me to this patch.
Is it on someones todo inbox, or can someone commit it? The last comment
reads like go is good to go.

We'll find out about the sanitizing thing when someone with more go
knownledge runs into this I guess.

Petter <petter@mykolab.ch> writes:

> On 2016-08-20 02:07, Leo Famulari wrote:
>> On Wed, Aug 17, 2016 at 10:54:36AM -0500, Alex Griffin wrote:
>>> Thanks for contributing! Your changes work for me, but it looks like
>>> your mail client mangled the formatting of your patch. So I produced a
>>> good patch with your changes, and added a copyright line and commit
>>> message for you. Hopefully that will make it easier for someone with
>>> commit access to look it over.
>>> 
>>> --
>>> Alex Griffin
>> 
>>> From f2f28e088f2a3f833251c2b31de7e6f531bcdf9a Mon Sep 17 00:00:00 2001
>>> From: Petter <petter@mykolab.ch>
>>> Date: Wed, 17 Aug 2016 10:27:04 -0500
>>> Subject: [PATCH] gnu: go: Update to 1.7.
>>> 
>>> * gnu/packages/golang.scm (go-1.6): Update to 1.7, with corresponding
>>>   minor changes to prebuild phase, and rename variable to...
>>>   (go-1.7): ...this new variable.
>>>   (go): Inherit from new "go-1.7".
>> 
>> I have a working Syncthing [0] on x86_64 with this patch.
>> 
>
> Good, my testing on a couple of small programs have been successful as 
> well.
>
>> I noticed this during the test suite:
>> 
>> ##### ../misc/cgo/testsanitizers
>> skipping msan tests: -fsanitize=memory not supported
>> gcc: error: -fsanitize=thread linking must be done with -pie or -shared
>> skipping tsan tests: -fsanitizer=thread build failed
>> 
>> I don't know whether or not that's a problem.
>> 
>
> Good catch, I did not notice this.
>
> It could be an error by the Go team, ref:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703230
>
> I don't know though if it would be correct for us in that case to add 
> -fPIC to this call if that would solve it.
>
>> [0] WIP branch:
>> https://github.com/lfam/guix/commits/contrib-syncthing
>> 
>>>  ;;; Copyright ?? 2016 Matthew Jordan <matthewjordandevops@yandex.com>
>>>  ;;; Copyright ?? 2016 Andy Wingo <wingo@igalia.com>
>>>  ;;; Copyright ?? 2016 Ludovic Court??s <ludo@gnu.org>
>>> +;;; Copyright ?? 2016 Petter <petter@mykolab.ch>
>> 
>> Petter, I noticed your original patch did not add a line like this.
>> Please confirm the name and email address you'd prefer to use.
>> Pseudoynms are fine.
>
> Alex got it right, this is the name and e-mail address I want to use.
>

-- 
ng0
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-09-06  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  9:34 [PATCH 1/1] Go: Update to 1.7 Petter
2016-08-17 15:54 ` Alex Griffin
2016-08-17 17:20   ` Petter
2016-08-20  0:27     ` Matthew Jordan
2016-08-20  0:07   ` Leo Famulari
2016-08-20 10:20     ` Petter
2016-09-06  9:45       ` ng0 [this message]
2016-09-06 19:14       ` Efraim Flashner

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=878tv57452.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=petter@mykolab.ch \
    /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).