From: Paul Eggert <eggert@cs.ucla.edu>
To: Po Lu <luangruo@yahoo.com>, bug-gnulib@gnu.org
Subject: Re: Follow up to last post
Date: Wed, 18 Jan 2023 14:18:25 -0800 [thread overview]
Message-ID: <0390f375-dfcb-458d-3200-639db8a41c02@cs.ucla.edu> (raw)
In-Reply-To: <87o7qw6jap.fsf@yahoo.com>
On 1/18/23 05:53, Po Lu wrote:
> + gl_CHECK_FUNCS_ANDROID([utimensat], [[#include <sys/stat.h>]])
> if test $ac_cv_func_utimensat = no; then
> HAVE_UTIMENSAT=0
> + REPLACE_UTIMENSAT=1
REPLACE_UTIMENSAT=1 means utimensat is present but broken and needs to
be replaced. However, $ac_cv_func_utimensat = no means utimensat is
absent. So I'm puzzled as to why REPLACE_UTIMENSAT=1 would be
appropriate here.
next prev parent reply other threads:[~2023-01-18 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o7qw6jap.fsf.ref@yahoo.com>
2023-01-18 13:53 ` Follow up to last post Po Lu
2023-01-18 22:18 ` Paul Eggert [this message]
2023-01-18 23:23 ` API levels and functions on Android Bruno Haible
2023-01-19 4:24 ` Paul Eggert
2023-01-19 10:27 ` Bruno Haible
2023-01-19 0:44 ` Follow up to last post Po Lu
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=0390f375-dfcb-458d-3200-639db8a41c02@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@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.
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).