From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libpcap: fix build failure without wchar
Date: Sat, 23 Jan 2021 18:06:09 +0100 [thread overview]
Message-ID: <20210123180609.7cb4cf6e@windsurf.home> (raw)
In-Reply-To: <20210122225221.3234679-1-fontaine.fabrice@gmail.com>
On Fri, 22 Jan 2021 23:52:21 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> libpcap requires c99 since version 1.10.0 and
> https://github.com/the-tcpdump-group/libpcap/commit/68e5ca3f4cbb66d687582ae9563009c87bf3d184
>
> However, this test will fail without wchar on:
>
> configure:3609: /home/buildroot/autobuild/run/instance-2/output-1/host/bin/arm-linux-gcc -std=gnu99 -c -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.c >&5
> conftest.c:52:9: error: unknown type name 'wchar_t'
> const wchar_t *name;
> ^~~~~~~
>
> So hardcode ac_cv_prog_cc_c99 as already done in numerous package such
> as apparmor, wireshark, xz, etc.
>
> Fixes:
> - http://autobuild.buildroot.org/results/6e87c25a0dccccf5e7ad03742597a0613f554506
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libpcap/libpcap.mk | 3 +++
> 1 file changed, 3 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2021-01-23 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 22:52 [Buildroot] [PATCH 1/1] package/libpcap: fix build failure without wchar Fabrice Fontaine
2021-01-23 17:06 ` 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=20210123180609.7cb4cf6e@windsurf.home \
--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 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.