From: John Kehayias <john.kehayias@protonmail.com>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: Josselin Poiret <dev@jpoiret.xyz>, Wilko Meyer <w@wmeyer.eu>,
Leo Famulari <leo@famulari.name>,
guix-devel@gnu.org
Subject: Re: Updates for Go
Date: Sat, 26 Aug 2023 00:29:57 +0000 [thread overview]
Message-ID: <87jztiir2g.fsf@protonmail.com> (raw)
Hi Katherine,
On Wed, Aug 23, 2023 at 10:12 AM, Katherine Cox-Buday wrote:
> On 8/22/23 8:24 AM, Felix Lechner via Development of GNU Guix and the
> GNU System distribution. wrote:
>> Hi Attila,
>>
>> On Tue, Aug 22, 2023 at 6:14 AM Attila Lendvai <attila@lendvai.name> wrote:
>>>
>>> currently the go build system in guix does not reuse build artifacts
>>
>> Can Golang reuse build artifacts?
>
> I don't think it's recommended right now. See discussion here:
>
> - <https://github.com/golang/go/issues/47788#issuecomment-1019562695>
> - <https://github.com/golang/go/issues/47788#issuecomment-1258773167>
>
> Summary:
>
> It sounds like due to the way the compiler can optimize code (e.g.
> inlining), `buildmode=shared` is not recommended, but in the future they
> are looking at allowing linking against a single shared library.
I've not been following in detail this discussion, but where do we currently stand? Is the proposed Go 1.21 patch basically ready? Should we create a branch and build job to start seeing how far we get in making 1.21 the default Go in Guix?
Like others, I have a few random Go packages (a bunch locally I really need to clean up too) and am not familiar with the language and our packaging much. Still, if I can help review/push some patches and get things moving, please let me know.
And thanks for all your work here, it is appreciated!
John
next reply other threads:[~2023-08-26 0:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 0:29 John Kehayias [this message]
2023-08-28 15:14 ` Updates for Go Katherine Cox-Buday
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 19:57 Katherine Cox-Buday
2023-08-16 17:25 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-17 14:25 ` Katherine Cox-Buday
2023-08-17 21:54 ` Wilko Meyer
2023-08-18 1:52 ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-08-19 11:31 ` Attila Lendvai
2023-08-21 18:14 ` Katherine Cox-Buday
2023-08-21 16:10 ` Katherine Cox-Buday
2023-08-21 17:53 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-21 18:17 ` Katherine Cox-Buday
2023-08-22 9:59 ` Josselin Poiret
2023-08-22 13:14 ` Attila Lendvai
2023-08-22 14:24 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-23 16:12 ` Katherine Cox-Buday
2023-08-27 15:41 ` wolf
2023-08-28 15:18 ` Katherine Cox-Buday
2023-08-22 11:01 ` Wilko Meyer
2023-08-22 18:06 ` david larsson
2023-08-23 15:35 ` Katherine Cox-Buday
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=87jztiir2g.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=cox.katherine.e@gmail.com \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=w@wmeyer.eu \
/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).