From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V3 1/3] prosody: bump to version 0.10.0
Date: Sun, 22 Oct 2017 12:37:59 +0200 [thread overview]
Message-ID: <20171022123759.7bf669f9@windsurf> (raw)
In-Reply-To: <20171022071716.792-1-francois.perrad@gadz.org>
Hello,
On Sun, 22 Oct 2017 09:17:14 +0200, Francois Perrad wrote:
> this version is not restricted to Lua 5.1
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
I'm sorry, but it still doesn't build, with the same build error:
table.c: In function ?Lpack?:
table.c:14:2: error: ?for? loop initial declarations are only allowed in C99 or C11 mode
for(int arg = n_args; arg >= 1; arg--) {
^
table.c:14:2: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
With the same defconfig:
BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2017.05-1078-g95b1dae.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_9=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_10=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_LUA=y
BR2_PACKAGE_PROSODY=y
# BR2_TARGET_ROOTFS_TAR is not set
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-22 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 7:17 [Buildroot] [V3 1/3] prosody: bump to version 0.10.0 Francois Perrad
2017-10-22 7:17 ` [Buildroot] [V3 2/3] prosody: remove tweaked configuration Francois Perrad
2017-10-22 7:17 ` [Buildroot] [V3 3/3] prosody: tweak configuration Francois Perrad
2017-10-22 10:38 ` Thomas Petazzoni
2017-10-22 10:46 ` Arnout Vandecappelle
2017-10-22 10:37 ` 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=20171022123759.7bf669f9@windsurf \
--to=thomas.petazzoni@free-electrons.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.