From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Problem on packaging qt-light extension for Chicken
Date: Thu, 07 Jan 2021 11:20:23 +0000 [thread overview]
Message-ID: <fSl5zawf0avEwuzBbCZBLjGUVka6mMG9XtLTeVzAlNhx9SViQK1HT_hS7fHe4KK5mrW_HSQFgeX8DLdW812-VXX2WsHWvKqecLlwvMiILWk=@elenq.tech> (raw)
In-Reply-To: <20210105140600.7bfe40e3@pantherx.org>
Hi,
> --8<---------------cut here---------------start------------->8---
> phase `unpack' succeeded after 0.0 seconds starting phase`patch-usr-bin-file'
> phase `patch-usr-bin-file' succeeded after 0.0 seconds starting phase`patch-source-shebangs'
> patch-shebang: ./qt-light/chicken-compile-qt-extension.scm: changing `/bin/sh' to`/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh'
> phase `patch-source-shebangs' succeeded after 0.0 seconds starting phase`setup-environment'
> phase `setup-environment' succeeded after 0.0 seconds starting phase`build'
>
> Error: extension not cached
> command "chicken-install" "-cached" "-no-install" "qt-light" failed with status 70
> --8<---------------cut here---------------end--------------->8---
>
When I saw the message I was puzzled and tried to work around your issues with no success.
I talked with who started the chicken buildsystem, and I was told the error is related with
some dependencies missing.
The error message should be clearer on this but it makes sense, the non-cached extension is
not qt-light but its deps.
The egg says:
--8<---------------cut here---------------start------------->8---
(dependencies bind protobj matchable miscmacros shell)
--8<---------------cut here---------------end--------------->8---
So you probably need to package that first.
Hope this helps. Good luck!
Ekaitz
next prev parent reply other threads:[~2021-01-07 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:36 Problem on packaging qt-light extension for Chicken Reza Alizadeh Majd
2021-01-07 11:20 ` Ekaitz Zarraga [this message]
2021-01-07 11:46 ` Reza Alizadeh Majd
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='fSl5zawf0avEwuzBbCZBLjGUVka6mMG9XtLTeVzAlNhx9SViQK1HT_hS7fHe4KK5mrW_HSQFgeX8DLdW812-VXX2WsHWvKqecLlwvMiILWk=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=help-guix@gnu.org \
--cc=r.majd@pantherx.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.
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).