Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-08-09
Date: Sat, 11 Aug 2018 12:25:29 +0200	[thread overview]
Message-ID: <20180811122529.664a5d96@windsurf> (raw)
In-Reply-To: <CANQCQpauBUYBkxNiw7CtHNOO3pOkxF0PGnjrP_HagUJ+N2q=hQ@mail.gmail.com>

Hello,

Adding Hollis, which I forgot in my initial e-mail. Hollis, please have
a look at the thread, there has been some other build errors on your
older build machine.

On Fri, 10 Aug 2018 19:20:47 -0500, Matthew Weber wrote:

> > This we've got only 10 failures on master, let's have a look at them.  
> > >      aarch64 |            host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/66c03506e10071ec44ca509304595f4f5150e4d9 |
> > >       mipsel |            host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/2b41afe7841feba626fc29c9474e82d9934e6173 |  
> >
> > Due to the use of atomic built-ins, not available in old compilers. I
> > would suggest to make all packages that depend on host-libselinux to
> > depend on the appropriate host gcc version.  
> 
> Hollis has sent a patch suggestion to keep libselinux compatible with
> older gcc.  Is there a preference on carrying the patch vs using a
> host gcc version detect ?  I didn't realize we had a way to depend on
> host gcc version.  I'll take a look at that but let me know which way
> is preferred.

If the issue can be worked around by a patch, it's nice because we
don't have to propagate the host gcc dependency to gazillions of
packages. However, Hollis patch wasn't that simple/trivial, it would be
nice to have it checked by upstream. Or maybe it's just me who isn't
familiar enough with the semantic of atomic intrinsics.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-11 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-09 Thomas Petazzoni
2018-08-10 22:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-11  0:20   ` Matthew Weber
2018-08-11 10:25     ` Thomas Petazzoni [this message]
2018-08-13 19:49   ` Peter Seiderer

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=20180811122529.664a5d96@windsurf \
    --to=thomas.petazzoni@bootlin.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