all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: 34499@debbugs.gnu.org
Subject: bug#34499: Fwd: Guile-gnome package broken in Guix
Date: Fri, 22 Feb 2019 19:09:26 +0100	[thread overview]
Message-ID: <65cae104-0c00-c9cc-7b79-44ff31d94b27@riseup.net> (raw)
In-Reply-To: <62956f1e-5010-1d4d-cce4-9b072a9f0dec@riseup.net>


[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]

On 2019-02-16 13:28, swedebugia wrote:
> On 2019-02-16 12:02, swedebugia wrote:
>> The files end up in profile/share/guile-gnome-2/... which is not in
>> guiles load path.
>>
>> The result of running the examples:
>> (first get it with guix build --source)
>>
>>
>> $ guile -s hello.scm
>> ...
>> ERROR: In procedure scm-error:
>> no code for module (gnome gobject)

I found the error!

Guile-gnome installs in such a way that it only works if you run it like
this: guile-gnome2 -s hello.scm

This seems undocumented and was unexpected. I expected "guile -s" to be
able to run also the modules installed by guile-gnome.

Should we add a note somewhere to avoid confusion and/or inform upstream
about this non-standard behavior?

-- 
Cheers Swedebugia


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2019-02-22 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <59cf0841-bc58-a4a2-80b1-a7f5808dde6b@riseup.net>
2019-02-16 11:02 ` bug#34499: Fwd: Guile-gnome package broken in Guix swedebugia
2019-02-16 12:28   ` swedebugia
2019-02-22 18:09     ` swedebugia [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=65cae104-0c00-c9cc-7b79-44ff31d94b27@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=34499@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 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.