unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita.karetnikov@gmail.com>
Cc: bug-guix@gnu.org
Subject: Re: daemon: No rule to make target `nix/libstore/schema.sql'
Date: Thu, 13 Dec 2012 22:20:46 +0100	[thread overview]
Message-ID: <871uet1wep.fsf@gnu.org> (raw)
In-Reply-To: <CAD15K4vHfX_UyX+zq+5d2fANYU9PXGiLH1R+nc8DLrs_r-dVhQ@mail.gmail.com> (Nikita Karetnikov's message of "Tue, 11 Dec 2012 14:55:29 +0300")

Hi,

Nikita Karetnikov <nikita.karetnikov@gmail.com> skribis:

>>> Also, how should I use it? It's in the
>>> 'remotes/origin/nix-integration' branch and I have to work in the
>>> 'master' branch.
>
>> Yeah, I hope to merge that branch soon.

Done.  :-)

> You misunderstood my question. I wanted to know how to use it instead
> of 'nix-worker --daemon'. Is it possible?

Now there’s a ‘guix-daemon’ binary that gets built.  Unlike
‘nix-daemon’, it does not check for nix.conf, and expects options to be
passed on the command-line.

>> Did you run ‘./bootstrap’ or ‘./nix/sync-with-upstream’?
>
> Yes, I did.
>
> # git checkout remotes/origin/nix-integration
>
> # autoreconf -vfi

You must run ‘./bootstrap’ before anything else.  It will take care of
running autoreconf.

> # cd nix
> # ./sync-with-upstream
> ./sync-with-upstream: line 62: cd: ../nix-upstream/src: No such file
> or directory

This is a sign that ‘nix-upstream’ did not get populated by
‘./bootstrap’ (which just does ‘git submodule update’.)

Thanks,
Ludo’.

  reply	other threads:[~2012-12-13 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 11:55 daemon: No rule to make target `nix/libstore/schema.sql' Nikita Karetnikov
2012-12-13 21:20 ` Ludovic Courtès [this message]
2012-12-13 21:56   ` Andreas Enge
2012-12-13 22:19     ` Andreas Enge
2012-12-13 22:55     ` Ludovic Courtès
2012-12-13 23:05       ` Andreas Enge
2012-12-14  9:52         ` Ludovic Courtès
2012-12-14 10:50           ` Andreas Enge
2012-12-14 21:12             ` 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=871uet1wep.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita.karetnikov@gmail.com \
    /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).