From: Gottfried <gottfried@posteo.de>
To: "(" <paren@disroot.org>, help-guix@gnu.org
Subject: Re: new version of paps (printing package for emacs)
Date: Sun, 8 Jan 2023 10:59:14 +0000 [thread overview]
Message-ID: <a7b1a30a-7522-7fa3-5f8e-c247972a3cc2@posteo.de> (raw)
In-Reply-To: <CPMQUTO0WC9F.4Z4FQZDST5HW@guix-framework>
[-- Attachment #1.1.1: Type: text/plain, Size: 967 bytes --]
Hi,
thanks
It started to bootstrap the file but failed.
phase `unpack' succeeded after 0.0 seconds
starting phase `bootstrap'
running './autogen.sh'
patch-shebang: ./autogen.sh: changing `/bin/sh' to
`/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/sh'
./autogen.sh: line 4: glib-gettextize: command not found
./autogen.sh: line 7: autoreconf: command not found
./autogen.sh: line 8: ./configure: No such file or directory
error: in phase 'bootstrap': uncaught exception:
%exception #<&invoke-error program: "./autogen.sh" arguments: ()
exit-status: 127 term-signal: #f stop-signal: #f>
phase `bootstrap' failed after 0.4 seconds
command "./autogen.sh" failed with status 127
Does that mean there is a bug in the file? and I have to wait until Guix
updates the package : paps?
Kind regards
Gottfried
Am 08.01.23 um 11:41 schrieb (:
> guix install paps --with-source=paps=file:///home/user/.../paps
--
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-01-08 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 10:15 new version of paps (printing package for emacs) Gottfried
2023-01-08 10:41 ` (
2023-01-08 10:42 ` (
2023-01-08 11:02 ` Gottfried
2023-01-08 11:35 ` (
2023-01-08 10:59 ` Gottfried [this message]
2023-01-08 11:01 ` (
2023-01-08 11:07 ` Gottfried
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=a7b1a30a-7522-7fa3-5f8e-c247972a3cc2@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=paren@disroot.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).