From: Thomas Danckaert <post@thomasdanckaert.be>
To: ben@sturm.com.au
Cc: guix-devel@gnu.org
Subject: Re: Packaging Jitsi SIP Communicator
Date: Wed, 08 Nov 2017 10:02:12 +0100 (CET) [thread overview]
Message-ID: <20171108.100212.241549577664824760.post@thomasdanckaert.be> (raw)
In-Reply-To: <87vail5sgz.fsf@sturm.com.au>
From: Ben Sturmfels <ben@sturm.com.au>
Subject: Packaging Jitsi SIP Communicator
Date: Wed, 08 Nov 2017 15:01:32 +1100
>
> Date: Wed, 08 Nov 2017 15:01:32 +1100
> Message: 2
> X-Mew: <3.3 body> Good PGP sign "Christopher Baines
> <mail@cbaines.net>" [unknown] UNDEFINED
>
> Hi Folks,
>
> I'm having some trouble packaging Jitsi (a VoIP client written in
> Java).
> The attached patch adds the package "jitsi", which completes the
> "build"
> phase, but fails as below. Ignoring for now that Jitsi is bundling
> a whole lot
> of dependencies, can someone help me understand what’s going on:
>
> [...]
>
> find-files: /gnu/store/kz7kwgm25xk83fc69immm80dazv9gb6x-jitsi-2.10:
> No such file or directory
>
> [...]
>
> builder for
> `/gnu/store/hxpb6xvx324d9i9kxc7ywfwwaz3zgs4z-jitsi-2.10.drv' failed
> to produce output path
> `/gnu/store/kz7kwgm25xk83fc69immm80dazv9gb6x-jitsi-2.10'
> @ build-failed
> /gnu/store/hxpb6xvx324d9i9kxc7ywfwwaz3zgs4z-jitsi-2.10.drv - 1
> builder for
> `/gnu/store/hxpb6xvx324d9i9kxc7ywfwwaz3zgs4z-jitsi-2.10.drv' failed
> to produce output path `
Hi,
These messages indicate that the build procedure did not create the
output directory, i.e. nothing was installed. So you should have a
look at the build procedure, and make sure there is an install phase
that creates and populates the output directory (available as
(assoc-ref %outputs "out")) with the items that were built.
Thomas
next prev parent reply other threads:[~2017-11-08 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 4:01 Packaging Jitsi SIP Communicator Ben Sturmfels
2017-11-08 8:56 ` Ludovic Courtès
2017-11-08 9:02 ` Thomas Danckaert [this message]
2017-11-08 10:09 ` julien lepiller
2017-12-19 6:05 ` Ben Sturmfels
2017-11-15 4:54 ` Chris Marusich
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=20171108.100212.241549577664824760.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=ben@sturm.com.au \
--cc=guix-devel@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).