bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: Re: API levels and functions on Android
Date: Wed, 18 Jan 2023 20:24:55 -0800	[thread overview]
Message-ID: <33c38598-bedd-9ac9-f6c7-d2206de59260@cs.ucla.edu> (raw)
In-Reply-To: <11306703.GINRyM86WL@nimes>

On 1/18/23 15:23, Bruno Haible wrote:
> Defining REPLACE_GLOB=1 despite HAVE_GLOB=0 will be the way to make Gnulib
> define 'rpl_glob' instead of 'glob', so that there is no conflict with libc.so.
> I still need to work out the details how this would/will work. So as to
> do things correctly on Android, while OTOH not adding lots of configure tests
> for the other platforms...

Thanks for looking into this.

On Android, should we always define REPLACE_WHATEVER when 'whatever' 
doesn't exist, at least for all the REPLACE_WHATEVER instances that 
currently exist in Gnulib? After all, 'whatever' might exist in some 
future Android version.

Would it make sense to wait until you've worked out the details, before 
installing patches like the REPLACE_UTIMENSAT=1 patch?

  reply	other threads:[~2023-01-19  4:25 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
2023-01-18 23:23     ` API levels and functions on Android Bruno Haible
2023-01-19  4:24       ` Paul Eggert [this message]
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:

  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=33c38598-bedd-9ac9-f6c7-d2206de59260@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=luangruo@yahoo.com \


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