From: ludo@gnu.org (Ludovic Courtès)
To: Deck Pickard <deck.r.pickard@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Hotfix (repeat)
Date: Tue, 25 Nov 2014 22:41:40 +0100 [thread overview]
Message-ID: <87mw7fvtyj.fsf@gnu.org> (raw)
In-Reply-To: <CAJ41eezu=NPqBEuEy76zWLr3QY3XQ0grq87Jw3JZX9fNDpjmLw@mail.gmail.com> (Deck Pickard's message of "Mon, 24 Nov 2014 16:40:52 +0100")
Deck Pickard <deck.r.pickard@gmail.com> skribis:
> On 23 Nov 2014 21:49, "Ludovic Courtès" <ludo@gnu.org> wrote:
>>
>> Deck Pickard <deck.r.pickard@gmail.com> skribis:
>>
>> > From 8e297904d80b39cd510ba0cced37acdb9b1aeb89 Mon Sep 17 00:00:00 2001
>> > From: nebuli <nebu@kipple>
>> > Date: Sat, 22 Nov 2014 19:58:24 +0100
>> > Subject: [PATCH 2/4] guix build: Add --max-jobs option (without handling
>> > code).
>> >
>> > * doc/guix.texi: Mention in the docs.
>> > * guix/scripts/build.scm: Extend (show-build-options-help) and
>> > (%standard-build-options) functions.
>>
>> Actually I had overlooked that this patch does nothing. :-)
>>
>> Could you send an updated version that passes the right option to
>> ‘set-build-options’?
>>
>
> No. Using '-c 0 -M 0' fails with cryptic message.
Setting max-jobs to 0 leads to:
--8<---------------cut here---------------start------------->8---
guix build: error: build failed: unable to start any build; either increase `--max-jobs' or enable distributed builds
--8<---------------cut here---------------end--------------->8---
That’s expected because it really asks for zero locally running build
jobs (something that is useful, for instance, on a Hydra front-end.)
Commit f6526eb addresses that in a simple way.
Thanks,
Ludo’.
prev parent reply other threads:[~2014-11-25 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 3:07 [PATCH] Hotfix (repeat) Deck Pickard
2014-11-23 20:16 ` Ludovic Courtès
2014-11-23 20:49 ` Ludovic Courtès
2014-11-24 15:40 ` Deck Pickard
2014-11-25 21:41 ` Ludovic Courtès [this message]
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=87mw7fvtyj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=deck.r.pickard@gmail.com \
--cc=guix-devel@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).