unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: ng0 <ng0@infotropique.org>
Cc: 27900@debbugs.gnu.org
Subject: bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository
Date: Tue, 1 Aug 2017 11:19:29 +0200	[thread overview]
Message-ID: <20170801111929.378f1312@scratchpost.org> (raw)
In-Reply-To: <20170801085922.hidhecwbpymfawyt@abyayala>

Hi ng0,

>        guix environment --fallback --ad-hoc guix autoconf automake@1.15.1 make guile guile-ssh pkg-config gcc-toolchain libgcrypt gnutls guile-json zlib bzip2 sqlite help2man gettext texinfo guile-git

I only ever do 

$ guix environment --fallback --pure guix

(The "--pure" is important)

and it works fine, bootstrapping too (via ./bootstrap - which invokes autoreconf).

I mean I guess your ad-hoc-everything way should be possible, but why would you do that?  It makes the setup flaky should the guix package ever change its inputs (I don't know whether it did in fact do that).

I do sometimes specify extra ad-hoc packages, like so:

$ guix environment --fallback --pure guix --ad-hoc guile-ncurses-with-gpm

The order of the arguments is sometimes important.  I think of "--ad-hoc" like "--" for many other UNIX commands (startx etc).

  reply	other threads:[~2017-08-01  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  8:59 bug#27900: broken checkout? can't run autotools (automake) anymore in guix repository ng0
2017-08-01  9:19 ` Danny Milosavljevic [this message]
2017-08-01  9:27   ` ng0

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=20170801111929.378f1312@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=27900@debbugs.gnu.org \
    --cc=ng0@infotropique.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).