From: Thomas Monjalon <thomas@monjalon.net>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>,
david.marchand@redhat.com
Subject: Re: [PATCH] doc: ensure sphinx output is reproducible
Date: Mon, 03 Jul 2023 17:29:38 +0200 [thread overview]
Message-ID: <5843892.MhkbZ0Pkbq@thomas> (raw)
In-Reply-To: <20230629125838.1995751-1-christian.ehrhardt@canonical.com>
29/06/2023 14:58, christian.ehrhardt@canonical.com:
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> By adding -j we build in parallel, to make building on multiprocessor
> machines more effective. While that works it does also break
> reproducible builds as the order of the sphinx generated searchindex.js
> is depending on execution speed of the individual processes.
[...]
> -if Version(ver) >= Version('1.7'):
> - sphinx_cmd += ['-j', 'auto']
What is the impact on build speed on an average machine?
next prev parent reply other threads:[~2023-07-03 15:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 12:58 [PATCH] doc: ensure sphinx output is reproducible christian.ehrhardt
2023-06-29 13:02 ` Christian Ehrhardt
2023-07-03 15:29 ` Thomas Monjalon [this message]
2023-07-06 12:49 ` Christian Ehrhardt
2023-11-27 16:45 ` Thomas Monjalon
2023-11-27 17:00 ` Bruce Richardson
2024-05-17 11:29 ` Luca Boccassi
2024-05-19 13:54 ` Thomas Monjalon
2024-05-19 16:36 ` Luca Boccassi
2024-05-19 17:13 ` Thomas Monjalon
2024-05-19 17:23 ` Luca Boccassi
2024-05-19 21:10 ` Thomas Monjalon
2024-05-20 9:53 ` Luca Boccassi
2024-05-20 15:39 ` Stephen Hemminger
2024-05-20 18:59 ` Thomas Monjalon
2024-05-26 11:30 ` Thomas Monjalon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5843892.MhkbZ0Pkbq@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.