unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kete <kete@ninthfloor.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: autoconf command not found
Date: Mon, 06 Jan 2014 08:26:21 -0500	[thread overview]
Message-ID: <2524580.KO2ijpDj7B@knossos> (raw)
In-Reply-To: <87y52tw9pb.fsf@gnu.org>

On Monday, January 06, 2014 01:56:00 PM Ludovic Courtès wrote:
> Where does this build log come from?

> Apparently the log above comes from a build, i.e., something run in the
> build environment (chroot, etc.)

Yes, this comes from './pre-inst-env guix build zsh'.

> What’s installed in the users’ profiles doesn’t matter here; what
> matters is the ‘inputs’ field of the package being built.  Apparently
> here ‘autoconf’ would need to be added as an input to that package.
> 
> However, that’s often a bad idea, but it’s hard to discuss without
> having more details.  Could you explain what you are trying to build and
> how, so we can better investigate?

Do you need more info?

PS – I built git guix inside of the guix 0.5 emacs, and I felt like that may 
have had unfavorable results. Inside git guix emacs, programs like the shells are coming from 
the OS packages instead of guix. I don't think that happened with guix 
0.5 inside its emacs. It's hard to explain. Emacs is loading from guix store.
The two /nix/store strings below are different:

$ ls -l ~/.guix-profile/bin
lrwxrwxrwx 1 guix-builder0 guix-builder 58 Dec 31  1969 /home/.../.guix-profile/bin -> /nix/store/qpb773jxk37yylcrm5yrmxpkb5lrc3ma-emacs-24.3/bin

$ guix package -I
...
emacs   24.3    out     /nix/store/c4khfda7zfmxmkgy9anxb3pdv8agzcsx-emacs-24.3
...

  reply	other threads:[~2014-01-06 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 12:30 autoconf command not found Kete
2014-01-06 12:56 ` Ludovic Courtès
2014-01-06 13:26   ` Kete [this message]
2014-01-06 15:13     ` Ludovic Courtès

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=2524580.KO2ijpDj7B@knossos \
    --to=kete@ninthfloor.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).