From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: bitset: use AC_C_INLINE
Date: Fri, 03 Jul 2020 12:19:56 +0200 [thread overview]
Message-ID: <1833366.KKtj3E0GAE@omega> (raw)
The files
lib/bitset.h
lib/bitset.c
lib/bitset/array.c
lib/bitset/list.c
lib/bitset/table.c
lib/bitset/vector.c
use 'static inline'. To prevent compilation errors with old compilers or with
"gcc -ansi" or such, configure needs to execute AC_C_INLINE.
2020-07-03 Bruno Haible <bruno@clisp.org>
bitset: Make sure the compiler does not barf on 'inline'.
* modules/bitset (configure.ac): New section.
diff --git a/modules/bitset b/modules/bitset
index 20c6806..21cde24 100644
--- a/modules/bitset
+++ b/modules/bitset
@@ -24,6 +24,9 @@ gettext-h
obstack
xalloc
+configure.ac:
+AC_REQUIRE([AC_C_INLINE])
+
Makefile.am:
lib_SOURCES += bitset.c bitset/array.c bitset/stats.c \
bitset/table.c bitset/list.c bitset/vector.c
reply other threads:[~2020-07-03 10:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1833366.KKtj3E0GAE@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@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).