From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5] package/i2c-tools: bump to version 4.0
Date: Fri, 15 Dec 2017 15:15:31 +0100 [thread overview]
Message-ID: <20171215151531.1b5a0015@windsurf> (raw)
In-Reply-To: <CA+_SqVYuSiM3_ZixwaMaowY1yaa525+Fj_Hpqup_Qk58ZpMMkQ@mail.gmail.com>
Hello,
On Fri, 15 Dec 2017 10:02:27 +0100, Angelo Compagnucci wrote:
> > After 5 or 6 rebuilds of the i2c-tools package this happened.
> >
> > Without your patch,
>
> You mean before bumping to version 4?
Yes, without your patch, i.e with the current version of i2c-tools in
Buildroot.
> > for i in $(seq 1 100) ; do echo "=== $i ===" ; rm -rf output/build/i2c-tools* ; make i2c-tools || break ; done
> >
> > With your patch applied, I've never been able to reach more than 5 or 6
> > iterations of the loop.
> >
> > Could you rework this, and test 100 iterations of building the i2c-tools package ?
>
> I built it now 3 times with my 8core machine with various -j settings,
> unfortunately I cannot reproduce:
>
> === 100 ===
> umask 0022 && make -C /home/angelo/DEV/BUILDROOT/buildroot
> O=/home/angelo/DEV/BUILDROOT/br_qemu_arm/. i2c-tools
So you built it 3 times, or 3 times my loop of 100 builds ?
> ls build/i2c-tools-4.0/
> CHANGES COPYING.LGPL eeprom include Makefile README tools
> COPYING eeprog eepromer lib py-smbus stub version.h
>
> Could you give me more details?
Well, I don't have more details to provide: I just build i2c-tools, and
it fails randomly.
Perhaps I should apply and see what the autobuilders have to say, i.e
if they agree with you (it builds) or with me (it fails randomly).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-15 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 13:23 [Buildroot] [PATCH v5] package/i2c-tools: bump to version 4.0 Angelo Compagnucci
2017-12-15 8:21 ` Thomas Petazzoni
2017-12-15 9:02 ` Angelo Compagnucci
2017-12-15 14:15 ` Thomas Petazzoni [this message]
2017-12-15 15:21 ` Angelo Compagnucci
2017-12-15 15:22 ` [Buildroot] FW: " Kees van Unen
2017-12-18 10:51 ` [Buildroot] " Thomas Petazzoni
2017-12-21 11:35 ` Angelo Compagnucci
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=20171215151531.1b5a0015@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.