From: Ricardo Wurmus <rekado@elephly.net>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: help-guix@gnu.org
Subject: Re: Guix can't build my dummy package definition
Date: Sun, 01 Mar 2020 17:15:21 +0100 [thread overview]
Message-ID: <87r1ycgig6.fsf@elephly.net> (raw)
In-Reply-To: <4D65396D-D8DA-42CC-9118-D470F9D5941D@korwin-zmijowski.fr>
Hi Jérémy,
> I've a package dummy definition in /tmp/def.scm:
>
> (use-modules
> (guix packages)
> (guix build-system emacs)
> (guix licenses)
> (guix git-download))
>
> (define-public ac-geiser
> (package
> (name "")
> (version "")
> (source
> (origin
> (uri
> (git-reference (url "")
> (commit "")))
> (method git-fetch)
> (sha256 (base32 ""))))
> (build-system emacs-build-system)
> (synopsis "")
> (description "")
> (license bsd-3)
> (home-page "")))
>
> Then when I do :
>
> ./pre-inst-env guix build -f /tmp/def.scm
>
> I get :
>
> guix build: error: #<unspecified>: not something we can build
This is because “define” (or “define-public”) does not return a value.
It returns an unspecified value.
When using “guix build” with a file then the file must evaluate to a
package value. This means it must end with a (package …) expression or
the name of a variable that is bound to a package expression.
You can fix this by either adding “ac-geiser” to the bottom of the file,
or by removing the (define-public ac-geiser …) wrapping around the
package expression.
--
Ricardo
next prev parent reply other threads:[~2020-03-01 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 12:58 Guix can't build my dummy package definition Jérémy Korwin-Zmijowski
2020-03-01 13:09 ` pelzflorian (Florian Pelz)
2020-03-01 14:50 ` Julien Lepiller
2020-03-01 15:49 ` Jérémy Korwin-Zmijowski
2020-03-01 16:15 ` Ricardo Wurmus [this message]
2020-03-01 16:25 ` Jérémy Korwin-Zmijowski
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=87r1ycgig6.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
/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.