unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 51981@debbugs.gnu.org
Subject: [bug#51981] [PATCH 0/1] Fix cross-compilation of packages that use go-build-system
Date: Sat, 14 May 2022 09:23:20 +0200	[thread overview]
Message-ID: <2d39676f4b73229ca654ce67ea3fce57b50edc53.camel@telenet.be> (raw)
In-Reply-To: <87bl2f6gti.fsf@rekahsoft.ca>

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]


> [PATCH 1/1] build: Fix cross compilation for go-build-system
Nice.

> +              ;; Set the output path for the build
> +              (string-append "-o="
> +                (assoc-ref outputs "out") "/bin/"
> +                (package-name->name+version
> +                  (strip-store-file-name (assoc-ref outputs "out"))))

Maybe add a comment on why the simpler "GOBIN" isn't used instead, such
that it won't be incorrectly simplified in the future.  I'm not sure if
this is correct though, what if the name of the binary differs from the
package name?  Or was if the go package has multiple binaries?


I found it at <https://patches.guix-patches.cbaines.net/project/guix-patches/patch/877dd36fvc.fsf@rekahsoft.ca/>,
but it doesn't seem to be in data.guix-patches.cbaines.net <https://data.guix-patches.cbaines.net/compare?base_commit=256c3e714a459af6db2343c9120c7180c5a14462&target_commit=9630c40d89c8f778c4961b49e30275f35a45948c> anymore,
maybe you could resend the patch as a v2?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      parent reply	other threads:[~2022-05-14  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19 19:59 [bug#51981] (no subject) Collin J. Doering
2021-11-19 20:37 ` [bug#51981] [PATCH 1/1] build: Fix cross compilation for go-build-system Collin J. Doering
2022-05-14  7:23 ` Maxime Devos [this message]

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=2d39676f4b73229ca654ce67ea3fce57b50edc53.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=51981@debbugs.gnu.org \
    /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).