unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging Jami progress
Date: Mon, 9 Dec 2019 23:17:29 +0100	[thread overview]
Message-ID: <20191209231729.7a253e9d@interia.pl> (raw)
In-Reply-To: <87wobac07c.fsf@ambrevar.xyz>

Dnia 2019-12-05, o godz. 15:32:23
Pierre Neidhardt <mail@ambrevar.xyz> napisał(a):

> - To call a custom function from the builder, you need to include the
>   module that defines it for the build system, e.g.
> 
>   (arguments
>     `(#:modules ((gnu packages telephony)
>                  ,@%gnu-build-system-modules)
>       ...)
> 
Tried luck with the procedure, but it seems I can't provide the module
I'm currently in to the "arguments" field - Guile said it couldn't find
code for the module: "no code for module (gnu packages jami)". I mean
in the jami.scm file, defining (gnu packages jami) module,
I can't give this module as an argument.
    (arguments
     `(#:modules ((gnu packages jami)
		   ,@%gnu-build-system-modules)
    ...)

By the way, I decided to move all Jami packages, procedures and
dependencies modified by the patches to a separate file -
jami.scm. It'll be much easier to maintain in this way.

The full error message:

The following derivation will be built:
   /gnu/store/an28ny48d6iyfn79j2fhqk7mvd6jmahq-pjproject-jami-2.9.drv
building
/gnu/store/an28ny48d6iyfn79j2fhqk7mvd6jmahq-pjproject-jami-2.9.drv...
Backtrace: 10 (primitive-load "/gnu/store/dj185gjiag94gk1clrj0158xcal?")
In ice-9/eval.scm:
   721:20  9 (primitive-eval (begin (use-modules (gnu # jami) # ?) ?))
In ice-9/psyntax.scm:
  1262:36  8 (expand-top-sequence ((begin (use-modules (gnu ?) ?) ?)) ?)
  1209:24  7 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
  1209:24  6 (parse _ (("placeholder" placeholder)) ((top) #(# # ?)) ?)
   285:10  5 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) ?)
In ice-9/boot-9.scm:
  3377:20  4 (process-use-modules _)
   222:17  3 (map1 (((gnu packages jami)) ((guix build #)) ((# ?)) ?))
  3378:31  2 (_ ((gnu packages jami)))
   2803:6  1 (resolve-interface _ #:select _ #:hide _ #:prefix _ # _ ?)
In unknown file:
           0 (scm-error misc-error #f "~A ~S" ("no code for modu?" ?) ?)

ERROR: In procedure scm-error:
no code for module (gnu packages jami)

Is there some kind of "this" for the module in guile I could use in
order to be able to invoke the jami-apply-dependency-patches procedure?
I exported it correctly using #:export (jami-apply-dependency-patches).


Jan Wielkiewicz

  parent reply	other threads:[~2019-12-09 22:17 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 20:47 Packaging Jami progress Jan Wielkiewicz
2019-11-04 22:48 ` Gábor Boskovits
2019-11-05 16:50   ` Jan Wielkiewicz
2019-11-05 17:31     ` Gábor Boskovits
2019-11-06 10:30     ` Pierre Neidhardt
2019-11-06 16:24       ` Jan Wielkiewicz
2019-11-06 17:07         ` Pierre Neidhardt
2019-11-07 19:02           ` Pierre Neidhardt
2019-11-07 19:55             ` Jan Wielkiewicz
2019-11-25 21:15             ` Jan
2019-11-26 10:07               ` Pierre Neidhardt
2019-11-26 19:33                 ` Jan
2019-11-26 20:12                   ` Pierre Neidhardt
2019-11-27 11:43                   ` zimoun
2019-11-30 18:21                     ` Jan
2019-11-30 18:38                       ` Pierre Neidhardt
2019-12-01 16:34                         ` Jan
2019-12-01 17:32                           ` Pierre Neidhardt
2019-12-01 18:25                             ` Jan
2019-12-03 15:44                             ` Jan Wielkiewicz
2019-12-03 16:04                               ` Pierre Neidhardt
2019-12-03 18:02                                 ` Jan
2019-12-03 18:37                                   ` Pierre Neidhardt
2019-12-03 18:38                                     ` Pierre Neidhardt
2019-12-04 14:36                                       ` Jan Wielkiewicz
2019-12-04 15:27                                         ` Pierre Neidhardt
2019-12-04 15:50                                           ` Jan Wielkiewicz
2019-12-04 16:06                                             ` Pierre Neidhardt
2019-12-04 16:56                                               ` Jan
2019-12-04 17:01                                                 ` Pierre Neidhardt
2019-12-04 17:22                                                   ` Jan Wielkiewicz
2019-12-05 14:32                                                     ` Pierre Neidhardt
2019-12-05 16:00                                                       ` Jan
2019-12-05 16:28                                                         ` Pierre Neidhardt
2019-12-09 22:17                                                       ` Jan Wielkiewicz [this message]
2019-12-10  8:57                                                         ` Pierre Neidhardt
2019-12-10  9:59                                                           ` Caleb Ristvedt
2019-12-10 10:45                                                             ` Pierre Neidhardt
2019-12-10 22:56                                                             ` Jan Wielkiewicz
2019-12-11  0:43                                                               ` Caleb Ristvedt
2019-12-11 16:33                                                                 ` Jan
2019-11-26 16:43               ` zimoun
2019-11-26 19:14                 ` Pierre Neidhardt
2019-11-07 19:10           ` Pierre Neidhardt
2019-11-07 19:47             ` Jan Wielkiewicz
2019-11-07 20:37               ` Pierre Neidhardt
2019-11-08 18:25                 ` Jan Wielkiewicz
2019-11-11  8:38                   ` Pierre Neidhardt
2019-11-11 10:14                     ` Jan Wielkiewicz
2019-11-11 10:45                       ` Pierre Neidhardt
2019-11-11 15:04                         ` Pierre Neidhardt
2019-11-11 15:38                           ` Jan
2019-11-14 16:48                             ` Pierre Neidhardt
2019-11-14 18:07                               ` Pierre Neidhardt
2019-11-14 20:40                                 ` Jan
2019-11-14 21:54                                   ` Pierre Neidhardt
2019-11-14 22:16                                     ` Jan
2019-11-15  9:07                                       ` Pierre Neidhardt
2019-11-16 12:48                                         ` Jan
  -- strict thread matches above, loose matches on Subject: below --
2019-12-15 20:12 Jan Wielkiewicz
2019-12-15 21:46 ` Ricardo Wurmus
2019-12-15 23:33   ` Jan Wielkiewicz
2019-12-21 23:28   ` Jan Wielkiewicz
2019-12-22  7:48     ` Ricardo Wurmus
2019-12-23 19:43       ` Jan
2019-12-25  1:34         ` Jan
2019-12-25  9:08           ` Efraim Flashner
2019-12-27 18:57           ` Jan Wielkiewicz
2019-12-27 20:32             ` Gábor Boskovits
2019-12-27 21:46               ` Jan Wielkiewicz
2019-12-28  9:40                 ` Pierre Neidhardt
2019-12-28 11:57                   ` Jan
2020-01-03  6:35                     ` Ricardo Wurmus
2020-01-01 15:22                   ` Jan
2020-01-03  6:33                     ` Ricardo Wurmus
2020-01-04  0:13                       ` Jan
2020-01-04 15:37                         ` Pierre Neidhardt
2020-01-06  1:49                           ` Jan
2020-01-06 18:23                           ` Jan
2020-01-06 19:49                             ` Jack Hill
2020-01-06 22:40                             ` zimoun
2020-01-07  7:48                               ` Pierre Neidhardt
2019-12-28  1:34           ` Jan Wielkiewicz
2019-12-28  9:53             ` Pierre Neidhardt
2019-12-28 12:00               ` Jan
2019-12-15 21:47 ` Jan Wielkiewicz

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=20191209231729.7a253e9d@interia.pl \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).