From: Mike Rosset <mike.rosset@gmail.com>
To: 40426@debbugs.gnu.org
Cc: D0dyBo0D0dyBo0@protonmail.com
Subject: [bug#40426] [PATCH] Add g-golf
Date: Tue, 14 Apr 2020 22:56:24 -0700 [thread overview]
Message-ID: <87imi1z46t.fsf@gmail.com> (raw)
In-Reply-To: <87eesq6iqq.fsf@cbaines.net>
Christopher Baines writes:
> Vitaliy Shatrov via Guix-patches via <guix-patches@gnu.org> writes:
>
> Does g-golf work with Guile 3 yet? If not, that's OK.
>
Hello Christopher, thanks for looking at this.
I did quick look at seeing if g-golf would work with guile 3.0. But I
ran into some issue with core module bindings. Since g-golf very much
WIP and like wise Nomad which is my primary use for g-golf is also
WIP. I've kept strictly to guile 2.2 for now to maintain a little extra
stability. I'll follow up on it when both nomad a g-golf are more
stable.
>
> I'd remove the #:tests? argument given the default value of #t is fine.
>
Not a problem either myself or Vitality will add a follow up
patch. This was orphaned since we just recently got tests working.
> I don't quite follow this GUILE_GGOLF_UNINSTALLED environment
> variable. Why not just use the absolute filename for the so file
> (without the extension I think)?
The problem here is that libg-golf is needed both at compile time and
runtime. So it can not be substituted say after the unpack stage. So
this just checks if GUILE_GGOLF_UNINSTALLED is set. Then it will
use libg-golf with normal dynamic-link search paths. Other wise it uses
the full store path.
I had discussed this scenario with the g-golf author, his
recommendation was to use this approach it's the same one used for the
guile-cv declaration. He's the author of guile-cv as well.
> Also, maybe delete the strip phase, as I don't think that does anything
> apart from producing a load of warnings.
>
I think the strip phase strips dynamic elf libraries as well? I
don't think it would hurt here to keep it for libg-golf at least?
Would you also be able to look at bug#40512 Christopher? That one is a
trivial review just some upstream bug fixes for Emacsy and a hash bump
in the package declaration. Technically not related to the patch. But
eventually I'll need both of these when I release the next version of
nomad.
Regards,
Mike
next prev parent reply other threads:[~2020-04-15 5:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 11:58 [bug#40426] [PATCH] Add g-golf Vitaliy Shatrov via Guix-patches via
2020-04-05 2:56 ` Mike Rosset
2020-04-14 18:10 ` Christopher Baines
2020-04-15 5:56 ` Mike Rosset [this message]
2020-04-15 8:24 ` Christopher Baines
2020-04-15 7:15 ` [bug#40426] v2, cleared Vitaliy Shatrov via Guix-patches via
2020-04-15 12:22 ` bug#40426: " Christopher Baines
2020-04-15 13:57 ` [bug#40426] [PATCH] Add g-golf Tobias Geerinckx-Rice via Guix-patches via
2020-04-15 16:47 ` Mike Rosset
2020-04-15 23:02 ` Mike Rosset
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=87imi1z46t.fsf@gmail.com \
--to=mike.rosset@gmail.com \
--cc=40426@debbugs.gnu.org \
--cc=D0dyBo0D0dyBo0@protonmail.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).