From: Luca Boccassi <bluca@debian.org>
To: "Bernhard M. Wiedemann" <bwiedemann@suse.de>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Sort list of entries in examples.dox
Date: Mon, 09 Oct 2017 17:12:09 +0100 [thread overview]
Message-ID: <1507565529.14973.1.camel@debian.org> (raw)
In-Reply-To: <9687ec77-a8ea-1d22-bb00-94b30dc23c28@suse.de>
On Mon, 2017-10-09 at 16:36 +0200, Bernhard M. Wiedemann wrote:
> On 2017-10-09 15:51, Luca Boccassi wrote:
> > If you are interested in reproducible builds please have a look at
> > this
> > patch series I submitted a while ago:
> >
> > http://dpdk.org/dev/patchwork/patch/28386/
> >
> > I have verified that those patches make the build reproducible on
> > Debian (x86/x86_64/arm64).
> >
> > Feedback from SUSE is very welcome!
>
> I am very interested in that topic.
>
> and would like to see http://dpdk.org/dev/patchwork/patch/28387/
> merged
> (instead of my patch).
In case you want to have a look, the DPDK page on the Debian
reproducible builds CI is the following:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dpdk.html
A new build in experimental is failing but it looks like it's due to a
different version of GCC being used between different builds.
> If https://savannah.gnu.org/bugs/?52076 gets merged, it will avoid
> the
> need for the others, except the above and
> http://dpdk.org/dev/patchwork/patch/28391/
> The latter I have not found necessary so far, but races are hard to
> reproduce anyway.
That last one was tricky, I'd say it happens one out of ten builds.
Thanks for all your work, having the GNU Make wildcard sort out of the
box would be really great!
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2017-10-09 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 13:20 Bernhard M. Wiedemann
2017-10-09 13:24 ` Bernhard M. Wiedemann
2017-10-09 13:51 ` Luca Boccassi
2017-10-09 14:36 ` Bernhard M. Wiedemann
2017-10-09 16:12 ` Luca Boccassi [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507565529.14973.1.camel@debian.org \
--to=bluca@debian.org \
--cc=bwiedemann@suse.de \
--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 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 NNTP newsgroup(s).