From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Nathan Dehnel <ncdehnel@gmail.com>
Subject: Re: "no code for module"
Date: Sun, 29 Dec 2019 00:03:19 +0100 [thread overview]
Message-ID: <218506A8-CC07-47D1-B1F1-A32E8E78E4DA@lepiller.eu> (raw)
In-Reply-To: <CAEEhgEsNMTLtO45mm_Fv9eYvMcmgZw62uoQbXK8t9g5S4GkyVA@mail.gmail.com>
Le 28 décembre 2019 23:28:50 GMT+01:00, Nathan Dehnel <ncdehnel@gmail.com> a écrit :
>I made a package which is basically a clone of the "hello" package
>example.
>
>(use-modules (guix packages)
> (guix download)
> (guix build-system gnu)
> (guix licenses))
>(define-public deadbeef
> (package
> (name "deadbeef")
> (version "1.8.2")
> (source (origin
> (method url-fetch)
> (uri (string-append
>"https://github.com/DeaDBeeF-Player/deadbeef/archive/" version
> ".tar.gz"))
> (sha256
> (base32
> "1wsx62gi1bfd9rx5br2gprq4q3sfp7iqj1inxhhiqjasbm85vg50"))))
> (build-system gnu-build-system)
> (synopsis "A music player for *nix-like systems and OS X")
> (description
> "GNU Hello prints the message \"Hello, world!\" and then exits. It
>serves as an example of standard GNU coding practices. As such, it
>supports
>command-line arguments, multiple languages, and so on.")
> (home-page "https://deadbeef.sourceforge.io/")
> (license gpl2)))
>
>I added it to a channel, and added the channel, then ran guix pull. I
>got this error:
>
>(repl-version 0 0)
>(exception misc-error (value #f) (value "~A ~S") (value ("no code for
>module" (deadbeef))) (value #f))
>
>Any idea what the problem is?
I think you need to make it an actual guile module, like this:
(define-module (deadbeef)
#:use-module (guix packages)
#:use-module (guix build-system gnu)
…)
Instead of simple use-modules. Does it make sense?
next prev parent reply other threads:[~2019-12-28 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 22:28 "no code for module" Nathan Dehnel
2019-12-28 22:57 ` Ricardo Wurmus
2019-12-28 23:03 ` Julien Lepiller [this message]
2019-12-28 23:17 ` Nathan Dehnel
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=218506A8-CC07-47D1-B1F1-A32E8E78E4DA@lepiller.eu \
--to=julien@lepiller.eu \
--cc=help-guix@gnu.org \
--cc=ncdehnel@gmail.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 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.