From: Thomas Klausner <wiz@NetBSD.org>
To: 24002@debbugs.gnu.org
Subject: bug#24002: configure: missing call to AC_C_FLEXIBLE_ARRAY_MEMBER
Date: Sat, 16 Jul 2016 11:13:04 +0200 [thread overview]
Message-ID: <20160716091303.GP23723@danbala.tuwien.ac.at> (raw)
Hi!
On NetBSD, the build of guile-2.0.12 breaks early because
FLEXIBLE_ARRAY_MEMBER is not defined:
In file included from strftime.c:33:0:
time-internal.h:48:14: error: 'FLEXIBLE_ARRAY_MEMBER' undeclared here (not in a function)
char abbrs[FLEXIBLE_ARRAY_MEMBER];
^
config.h has:
/* #undef FLEXIBLE_ARRAY_MEMBER */
I think the problem is that m4/gnulib-comp.m4 has:
if test "$HAVE_TIMEZONE_T" = 0; then
func_gl_gnulib_m4code_flexmember
fi
but on NetBSD, HAVE_TIMEZONE_T is 1 and so
func_gl_gnulib_m4code_flexmember is not called and
FLEXIBLE_ARRAY_MEMBER is not defined.
FLEXIBLE_ARRAY_MEMBER is used in time-internal.h which is included by:
lib/time_rz.c lib/timegm.c lib/strftime.c lib/mktime.c
so there might be more cases where this will break.
Cheers,
Thomas
next reply other threads:[~2016-07-16 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 9:13 Thomas Klausner [this message]
2017-03-01 8:26 ` bug#24002: configure: missing call to AC_C_FLEXIBLE_ARRAY_MEMBER Andy Wingo
2017-03-15 14:05 ` Thomas Klausner
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160716091303.GP23723@danbala.tuwien.ac.at \
--to=wiz@netbsd.org \
--cc=24002@debbugs.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).