unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: How to install prerelease package versions (particularly Emacs)
Date: Wed, 11 Apr 2018 21:23:06 +0530	[thread overview]
Message-ID: <87tvsh3fkt.fsf@gmail.com> (raw)
In-Reply-To: <87muypvhh3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]


Mathieu Lirzin <mthl@gnu.org> writes:

> With the ‘#:recursive?’ keyword option set to #t, ‘local-file’ should
> work for directories.

Indeed, thanks for pointing out.

I tried and it failed with

	starting phase `configure'
	source directory: "/tmp/guix-build-emacs-dev-26.0.91.drv-0/source" (relative from build: ".")
	build directory: "/tmp/guix-build-emacs-dev-26.0.91.drv-0/source"
	configure flags: ("CONFIG_SHELL=/gnu/store/icz3hd36aqpjz5slyp4hhr8wsfbgiml1-bash-minimal-4.4.12/bin/bash" "SHELL=/gnu/store/icz3hd36aqpjz5slyp4hhr8wsfbgiml1-bash-minimal-4.4.12/bin/bash" "--prefix=/gnu/store/iaipasvi8dys79ms3y0axvwwdfnd31dq-emacs-dev-26.0.91" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu")
	configure: WARNING: unrecognized options: --enable-fast-install
	./configure: line 3350: config.log: Permission denied
	./configure: line 3360: config.log: Permission denied
	phase `configure' failed after 0.1 seconds

I inspected the content of
"/tmp/guix-build-emacs-dev-26.0.91.drv-0/source": many files are
missing, among others "configure".

I am very confused...

--
Pierre Neidhardt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 483 bytes --]

  reply	other threads:[~2018-04-11 15:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  0:00 How to install prerelease package versions (particularly Emacs) Jorge
2018-03-03 10:24 ` Oleg Pykhalov
2018-03-19  4:13   ` Chris Marusich
2018-03-26 18:42     ` Pierre Neidhardt
2018-03-27  9:51       ` Ludovic Courtès
2018-03-27 12:24         ` Clément Lassieur
2018-03-27 15:33         ` Oleg Pykhalov
2018-03-27 17:46           ` Marius Bakke
2018-03-27 20:57           ` Ludovic Courtès
2018-03-28  7:12             ` Oleg Pykhalov
2018-03-30  7:06               ` Pierre Neidhardt
2018-03-30 12:13                 ` Mathieu Lirzin
2018-03-30 12:19                   ` Pierre Neidhardt
2018-03-30 13:08                     ` Mathieu Lirzin
2018-04-11 15:53                       ` Pierre Neidhardt [this message]
2018-04-12  8:29                         ` Chris Marusich
2018-04-12  9:12                           ` Pierre Neidhardt
2018-04-12 12:57                             ` Ricardo Wurmus
2018-04-12 13:21                               ` Pierre Neidhardt
2018-04-13  5:27                             ` Chris Marusich
2018-04-13  5:57                         ` Carlo Zancanaro
2018-04-01 14:09                 ` Oleg Pykhalov
2018-04-11 16:00                   ` Pierre Neidhardt
2018-04-12  8:28                     ` Chris Marusich
2018-04-12  8:32                       ` Pierre Neidhardt
2018-04-11 15:57               ` Pierre Neidhardt
2018-04-12  6:06                 ` Pierre Neidhardt
2018-04-05 15:53       ` Jorge
2018-04-05 19:36         ` Pierre Neidhardt
2018-03-03 13:46 ` Jorge

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=87tvsh3fkt.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=mthl@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.
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).