Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 18 Dec 2017 11:51:50 +0100	[thread overview]
Message-ID: <20171218115150.71216129@windsurf> (raw)
In-Reply-To: <CA+_SqVZd14XeQ8Quw_se8N12ePYSMffgMH0=QDuegnx4BausHg@mail.gmail.com>

Hello,

On Fri, 15 Dec 2017 16:21:10 +0100, Angelo Compagnucci wrote:

> > Yes, without your patch, i.e with the current version of i2c-tools in
> > Buildroot.  
> 
> Looking at the git history, the makefile is not changed that much but,
> If I remember correctly, it had two bugs:
> 
> The first one was with parallel builds and fixed here [1] by the upstream.
> The second one was with shared libraries when BR2_STATIC_LIBS is selected.
> Imho these bugs were present before version 4.
> 
> Want we to keep version 3.1.2?

No we want to bump, but not if that introduces regressions.

> >> === 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 ?  
> 
> ^^^ That "=== 100 ===" means the last row of the output from your loop.
> So I run at least 3 times your loop and something more meanwhile.

OK. Weird.

> >> 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).  
> 
> I hope it works!

I'd like someone else in the Buildroot community to test your patch and
see if the parallel build problems are also reproducible. Anyone
available to test Angelo's patch?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2017-12-18 10:51 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
2017-12-15 15:21       ` Angelo Compagnucci
2017-12-15 15:22         ` [Buildroot] FW: " Kees van Unen
2017-12-18 10:51         ` Thomas Petazzoni [this message]
2017-12-21 11:35           ` [Buildroot] " 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=20171218115150.71216129@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox