unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: jonathan@terracrypt.net
To: help-guix@gnu.org
Subject: Re: Missing .so for guile-aiscm
Date: Fri, 30 Dec 2022 23:40:41 -0500	[thread overview]
Message-ID: <878rioxjv5.fsf@lambdacrypt.mail-host-address-is-not-set> (raw)
In-Reply-To: <87zgb48k9y.fsf@terracrypt.net>

Ah, hmm - so I think I partly figured out why. (At least, enough to move
forward with what I'm trying to do.) The Guile package in Guix isn't
configured to look in GUILE_EXTENSIONS_PATH for native extensions. I
managed to work around this by doing this in a manifest for my project:

#+begin_src scheme
(define-public guile-search
  (package
    (inherit guile-3.0)
    (native-search-paths
     (list (search-path-specification
            (variable "GUILE_EXTENSIONS_PATH")
            (files (list "lib/guile/3.0/extensions")))))))
#+end_src

That said... is there a reason the Guile package doesn't already look
here by default?


      reply	other threads:[~2022-12-31  4:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31  0:29 Missing .so for guile-aiscm Jonathan Frederickson
2022-12-31  4:40 ` jonathan [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=878rioxjv5.fsf@lambdacrypt.mail-host-address-is-not-set \
    --to=jonathan@terracrypt.net \
    --cc=help-guix@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.
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).