all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew Jordan <matthewjordandevops@yandex.com>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [Patch] go@1.4
Date: Thu, 02 Jun 2016 12:29:26 -0400	[thread overview]
Message-ID: <87lh2nh7vd.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87pos0auvd.fsf@igalia.com>


Hey Andy and everyone,

Just a quick update, will send more details, or some patches later.

Just finished up building go@1.5.4, thanks to last bit you sent. The
runpath now validates in both go@1.4.3 and go@1.5.4.  All enabled test
now pass.

>> 	if Linkshared {
>> 		seenDirs := make(map[string]bool)
>> 		seenLibs := make(map[string]bool)
>> 		addshlib := func(path string) {
>> 			dir, base := filepath.Split(path)
>> 			if !seenDirs[dir] {
>> 				argv = append(argv, "-L"+dir)
>> 				if !rpath.set {
>> 					argv = append(argv, "-Wl,-rpath="+dir)
>> 				}
>
> This one.  I do a substitute* of !rpath.set to "true" :)

Personally I have no problem with it, already added some code for it.

> Anyway.  I think it is a sufficiently innocuous of a fix that it will
> allow us to merge Go.  Let us call this yak shaved and get Go in.  WDYT?

I'm game for anything practical, but we'll see what the reviewers have
to say when I submit the updated patches.

Also do you mind if I add you name and email an Co-author of these three
packages?

Sincerely,

--
Matthew Jordan
Sent with my mu4e

  reply	other threads:[~2016-06-02 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 19:39 [Patch] go@1.4 Matthew Jordan
2016-05-29 17:49 ` Andy Wingo
2016-05-29 18:48   ` Matthew Jordan
2016-06-02  7:54   ` Andy Wingo
2016-06-02 16:29     ` Matthew Jordan [this message]
2016-06-03  8:13       ` Andy Wingo

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=87lh2nh7vd.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me \
    --to=matthewjordandevops@yandex.com \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.