All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Bobroff <sam.bobroff@au1.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of autobuild failures 18-19/11
Date: Fri, 25 Nov 2016 11:51:28 +1100	[thread overview]
Message-ID: <20161125005128.GA9317@tungsten.ozlabs.ibm.com> (raw)
In-Reply-To: <4ed19823-030d-7f1d-0be9-549651d21a3b@mind.be>

On Thu, Nov 24, 2016 at 09:48:15PM +0100, Arnout Vandecappelle wrote:
> 
> 
> On 21-11-16 00:18, Sam Bobroff wrote:
> > Really, the right approach would probably be to change the compiler
> > flags so that it's not combining altivec with -std=c99 (e.g. change
> > -std=c99 to -std=gnu99, which also fixes the issue for me) but I'm
> > concerned that doing it that way might have unintended side effects
> > since I don't know exactly what those flags change or why the package is
> > setting c99 in the first place.
> 
>  Packages usually set --std=cNN to give some kind of portability guarantee.
> There normally shouldn't be a difference when compiling with --std=gnu. There
> are no guarantees, of course, but it should be pretty safe.

OK sounds good, I'll send a patch doing this.

Cheers,
Sam.

  reply	other threads:[~2016-11-25  0:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 19:23 [Buildroot] Analysis of autobuild failures 18-19/11 Arnout Vandecappelle
2016-11-19 20:55 ` Romain Naour
2016-11-20 15:24 ` Arnout Vandecappelle
2016-11-20 23:18 ` Sam Bobroff
2016-11-24 20:48   ` Arnout Vandecappelle
2016-11-25  0:51     ` Sam Bobroff [this message]
2016-11-21 11:21 ` Waldemar Brodkorb
2016-11-21 23:40   ` Arnout Vandecappelle
2016-11-23 11:37     ` Waldemar Brodkorb
2016-11-23 12:06       ` Arnout Vandecappelle
2016-11-25  0:26         ` Waldemar Brodkorb
2016-11-21 11:44 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2016-11-21 14:51 ` Alexey Brodkin
2016-11-21 22:08 ` [Buildroot] " Thomas Petazzoni
2016-11-21 23:38   ` Arnout Vandecappelle
2016-11-22  8:26     ` Thomas Petazzoni
2016-11-22 15:30       ` Arnout Vandecappelle
2016-11-22 15:38         ` Thomas Petazzoni
     [not found]           ` <CANLo3Ji8MiH29tYCwmpu4KMDJkcm7-75EUGK1mq3e8Tnih6aZQ@mail.gmail.com>
2016-11-22 19:08             ` Romain Naour

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=20161125005128.GA9317@tungsten.ozlabs.ibm.com \
    --to=sam.bobroff@au1.ibm.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.