All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libdrm: fix building if GCC's C standard is not gnu99
Date: Fri, 3 Jul 2015 00:22:51 +0200	[thread overview]
Message-ID: <20150702222251.GL3838@free.fr> (raw)
In-Reply-To: <20150703001946.03f906e7@gmx.net>

Peter, All,

On 2015-07-03 00:19 +0200, Peter Seiderer spake thusly:
> On Fri, 3 Jul 2015 00:05:34 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > On 2015-07-02 23:46 +0200, Arnout Vandecappelle spake thusly:
> > > On 07/02/15 23:12, Peter Seiderer wrote:
> > > [snip]
> > > > From build/libv4l-1.6.2/config.log:
> > > > 
> > > > configure:4709: checking for .../host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc option to accept ISO C99
> > > > configure:4858: .../host/usr/bin/arm-buildroot-linux-uclibcgnueabi-gcc -std=gnu99 -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64   -Os  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5
> > > > conftest.c:54:9: error: unknown type name 'wchar_t'
> > > >    const wchar_t *name;
> > > > 
> > > > 
> > > > The C99 detection problem seems more related to missing wchar_t type support than the compiler option?
> > > 
> > >  Good catch!
> > > 
> > > [Adding Waldemar for uClibc input]
> > > 
> > >  The configure script does include wchar.h, but it seems that wchar_t doesn't
> > > get defined after all... Waldemar, any idea?
> > 
> > No wchar support in the toolchain, maybe?
> > 
> > Peter, can you confirm your toolchain is missing wchar (BR2_USE_WCHAR)?
> >
> 
> Used up to date raspberrypi_defconfig, no wchar support enabled:

Note that I just updated it two days ago. ;-)

> # BR2_TOOLCHAIN_BUILDROOT_WCHAR is not set

OK, thanks; that explains it.

Still ,that autoconf test is broken... :-(

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-07-02 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 18:05 [Buildroot] [PATCH 1/1] package/libdrm: fix building if GCC's C standard is not gnu99 Bernd Kuhls
2015-07-02 20:40 ` Yann E. MORIN
2015-07-02 21:12 ` Peter Seiderer
2015-07-02 21:46   ` Arnout Vandecappelle
2015-07-02 22:05     ` Yann E. MORIN
2015-07-02 22:19       ` Peter Seiderer
2015-07-02 22:22         ` Yann E. MORIN [this message]
2015-07-04 12:14 ` 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=20150702222251.GL3838@free.fr \
    --to=yann.morin.1998@free.fr \
    --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.