From: swedebugia <swedebugia@riseup.net>
To: 34499@debbugs.gnu.org
Subject: bug#34499: Fwd: Guile-gnome package broken in Guix
Date: Sat, 16 Feb 2019 12:02:10 +0100 [thread overview]
Message-ID: <faf488e1-9f75-1ff3-0cc2-89cd6c54fbfb@riseup.net> (raw)
In-Reply-To: <59cf0841-bc58-a4a2-80b1-a7f5808dde6b@riseup.net>
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)
-------- Forwarded Message --------
Subject: Guile-gnome package broken in Guix
Date: Sat, 16 Feb 2019 11:47:13 +0100
From: swedebugia <swedebugia@riseup.net>
To: guile-gtk-general@gnu.org
Hi
I would really like to start creating my first gtk program with guile.
The package guile-gnome in guix is unfortunately broken and the docs and
examples are missing.
I tried fixing the package but it seems I do not understand gtk nor
autotools well enough to succeed.
I got these questions:
* why are there no TARGET_DIR in the makefiles?
* what is the purpose of the "guilesite" variable?
* what is the purpose of the files in /defs/gnome/defs ? The makefile
there seems to try to check for stuff in DEFS_HEADER_DIR = /usr/include
Thanks in advance.
--
Cheers Swedebugia
next parent reply other threads:[~2019-02-16 11:03 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 ` swedebugia [this message]
2019-02-16 12:28 ` bug#34499: Fwd: Guile-gnome package broken in Guix swedebugia
2019-02-22 18:09 ` swedebugia
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=faf488e1-9f75-1ff3-0cc2-89cd6c54fbfb@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 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).