Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] valgrind: fix uclibc c99 support detection
Date: Sun, 28 Oct 2018 17:32:34 +0100	[thread overview]
Message-ID: <20181028173234.33bec578@windsurf> (raw)
In-Reply-To: <20181028093957.20543-1-ps.report@gmx.net>

Hello,

On Sun, 28 Oct 2018 10:39:57 +0100, Peter Seiderer wrote:
> Fixes [1]:
> 
>   checking for /home/peko/autobuild/instance-0/output/host/bin/powerpc-linux-gcc option to accept ISO C99... unsupported
>   configure: error: Valgrind relies on a C compiler supporting C99
> 
> with the following in the valgrind-3.14.0/config.log:
> 
>   configure:5517: checking for .../host/bin/powerpc-linux-gcc option to accept ISO C99
>   configure:5666: .../host/bin/powerpc-linux-gcc -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Os -fno-stack-protector -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5
>   conftest.c:55:9: error: unknown type name 'wchar_t'
>      const wchar_t *name;
>            ^~~~~~~
> 
> [1] http://autobuild.buildroot.net/results/b25013f785a11f07e8da3735741b96036712f42a
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
>  package/valgrind/valgrind.mk | 3 +++
>  1 file changed, 3 insertions(+)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-10-28 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28  9:39 [Buildroot] [PATCH v1] valgrind: fix uclibc c99 support detection Peter Seiderer
2018-10-28  9:44 ` Thomas Petazzoni
2018-10-28 11:16   ` Peter Seiderer
2018-10-28 16:32 ` Thomas Petazzoni [this message]

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=20181028173234.33bec578@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