From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: prefetch tarballs in a batch
Date: Sun, 11 May 2014 21:17:42 +0200 [thread overview]
Message-ID: <87a9aoqg4p.fsf@gnu.org> (raw)
In-Reply-To: <87ha4ws6za.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sun, 11 May 2014 18:52:25 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>>>> Does the installation seem sane, basically? Do ‘guix build’, ‘guix
>>>> package’ etc. work somehow, or not even?
>
>>> Turns out I can’t even build ‘hello’
>
>> Please say exactly why you “can’t”.
>
> Currently, it fails due to the “bad file descriptor” error.
OK.
>> Why the hell do you keep deleting the store? :-)
>
> I want to make sure that ‘prefetch’ downloads all the needed tarballs.
> Since I don’t use Guix on that machine, I delete the store each time
> instead of using a different prefix.
Ah, OK.
>>> SQLite header and source version mismatch
>>> 2011-11-01 00:52:41 c7c6050ef060877ebe77b41d959e9df13f8c9b5e
>>> 2013-09-03 17:11:13 7dd4968f235d6e1ca9547cda9cf3bd570e1609ef
>
>>> This was discussed before and should be fixed by upgrading SQLite.
>
>> OK. Can you report how things go one that is fixed?
>
>> 1. Run ‘git show c0412fedf | patch -p1 -R’, and then confirm that the
>> problem disappears.
>
>> 2. Run ‘git reset --hard’, edit config.h, and comment out the HAVE_
>> macros corresponding to the functions listed in c0412fedf, one at a
>> time.
>
> What would be a reliable way to run the testsuite after each of the
> above steps? Would ‘make clean && autoreconf -vfi && make && make
> check’ be sufficient?
‘make check’ should be sufficient: it will rebuild ‘configure’, re-run
it, rebuild guix-daemon, etc.
Ludo’.
next prev parent reply other threads:[~2014-05-11 19:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 23:25 Proposal: prefetch tarballs in a batch Nikita Karetnikov
2014-03-28 13:23 ` Ludovic Courtès
2014-04-01 23:23 ` Nikita Karetnikov
2014-04-02 12:57 ` Ludovic Courtès
2014-04-02 22:37 ` Nikita Karetnikov
2014-04-03 7:24 ` Ludovic Courtès
2014-04-09 22:29 ` Nikita Karetnikov
2014-04-10 8:21 ` Ludovic Courtès
2014-04-12 20:19 ` Nikita Karetnikov
2014-04-12 22:44 ` Ludovic Courtès
2014-04-24 21:20 ` Nikita Karetnikov
2014-04-25 11:51 ` Ludovic Courtès
2014-04-25 12:04 ` Ludovic Courtès
2014-05-06 12:37 ` Nikita Karetnikov
2014-05-06 20:02 ` Ludovic Courtès
2014-05-07 23:14 ` Nikita Karetnikov
2014-05-08 16:35 ` Ludovic Courtès
2014-05-11 14:52 ` Nikita Karetnikov
2014-05-11 19:17 ` Ludovic Courtès [this message]
2014-09-02 21:06 ` Ludovic Courtès
2014-09-02 22:05 ` Nikita Karetnikov
2014-09-02 21:04 ` 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=87a9aoqg4p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nikita@karetnikov.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).