unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 65319@debbugs.gnu.org
Subject: bug#65319: compilation error on Android (Termux)
Date: Wed, 16 Aug 2023 11:50:11 +0200	[thread overview]
Message-ID: <4343512.eakKr8yo8t@nimes> (raw)
In-Reply-To: <878rabllty.fsf@yahoo.com>

Po Lu wrote:
> Does Gnulib guarantee that the gl_CHECK_FUNCS_ANDROID stuff will
> continue to exist in the future?  If so, I'm inclined towards using
> that.

Yes. This macro is used over 100 times in Gnulib, has not seen any
problem reports in the last 6 months, and is prefixed with 'gl_'
not '_gl_'. Therefore it's very unlikely to go away.

Note this macro's documentation:

...
dnl Thus, the question "does the OS have the function func" has three possible
dnl answers:
dnl   - yes, in all versions starting from the given API level,
dnl   - no, in no version,
dnl   - not in the given API level, but in a later version of Android.
...
dnl This macro sets two variables:
dnl   - gl_cv_onwards_func_<func>   to yes / no / "future OS version"
dnl   - ac_cv_func_<func>           to yes / no / no
dnl The first variable allows to distinguish all three cases.
dnl The second variable is set, so that an invocation
dnl   gl_CHECK_FUNCS_ANDROID([func], [[#include <foo.h>]])
dnl can be used as a drop-in replacement for
dnl   AC_CHECK_FUNCS([func]).

Bruno








  reply	other threads:[~2023-08-16  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 20:28 bug#65319: compilation error on Android (Termux) Bruno Haible
2023-08-16  1:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16  1:49   ` Bruno Haible
2023-08-16  3:15     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-16  9:50       ` Bruno Haible [this message]
2023-08-16 12:33         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4343512.eakKr8yo8t@nimes \
    --to=bruno@clisp.org \
    --cc=65319@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).