Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openocd: bump to 0.9.0
Date: Tue, 1 Dec 2015 14:20:54 +0200	[thread overview]
Message-ID: <20151201122054.GG2193@tarshish> (raw)
In-Reply-To: <CAGm1_ksRfJUZt=1Hm8Lzn7C=hCSJwgENG5ac6jLfRO06mt_gsg@mail.gmail.com>

Hi Yegor,

On Tue, Dec 01, 2015 at 12:25:46PM +0100, Yegor Yefremov wrote:
> On Tue, Dec 1, 2015 at 11:56 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > On Tue, 1 Dec 2015 11:33:25 +0100, Yegor Yefremov wrote:
> >
> >> Commit message states: Pass -std=gnu99, needed to build with a basic toolchain.
> >>
> >> I've commented this like and could successfully compile with musl +
> >> gcc 4.9.3 and also with Linaro ARM 2015.08 (GCC 5.x).
> >>
> >> @Thomas and @Claudio: any idea, what configuration produced compiling issues?
> >
> > Can you try with
> > http://autobuild.buildroot.org/toolchains/configs/br-arm-basic.config ?
> > This is what I call a "basic" toolchain, i.e a minimal uClibc toolchain
> > with no wchar and al. enabled.
> 
> Compilation *fails* without gnu99 with basic toolchain.

Just curious, do you have any idea why the build fails, and how -std=gnu99 
fixes the problem?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-12-01 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  8:52 [Buildroot] [PATCH] openocd: bump to 0.9.0 yegorslists at googlemail.com
2015-12-01  9:58 ` Baruch Siach
2015-12-01 10:33   ` Yegor Yefremov
2015-12-01 10:56     ` Thomas Petazzoni
2015-12-01 11:25       ` Yegor Yefremov
2015-12-01 12:20         ` Baruch Siach [this message]
2015-12-01 13:29           ` Yegor Yefremov
2015-12-01 13:56             ` Yegor Yefremov
2015-12-01 16:43 ` Thomas Petazzoni

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=20151201122054.GG2193@tarshish \
    --to=baruch@tkos.co.il \
    --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