bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org
Subject: Re: Android NDK r26 and utmpx
Date: Sun, 21 Jan 2024 13:11:59 +0800	[thread overview]
Message-ID: <87mssztgm8.fsf@yahoo.com> (raw)
In-Reply-To: <a6019e22-2b2d-4301-866f-81dd8fe38fc9@cs.ucla.edu> (Paul Eggert's message of "Sat, 20 Jan 2024 20:04:14 -0800")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 2024-01-20 19:38, Po Lu wrote:
>> the problem affects the boot-time module rather than
>> readutmp, which Emacs doesn't import.  And in the words of Bruno, a
>> functional utmp(x) might appear in Android someday, which binaries
>> compiled today should take advantage of wherever available.
>
> Oh, I see I was barking up the wrong tree.  How about the attached
> patch instead? Again, it's not installed into Gnulib and is not tested
> on Android.

I haven't tested this yet, but something tells me that the proper course
of action is to guarantee that the code which worked under NDK r25 is
enabled under r26, in the sense of falling back to the HAVE_UTMP_H
conditional (in readutmp.h) if functions inside utmpx.h can't be linked
against.

Thanks.


  reply	other threads:[~2024-01-21  5:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v87ntq4m.fsf.ref@yahoo.com>
2024-01-21  1:46 ` Android NDK r26 and utmpx Po Lu
2024-01-21  3:04   ` Paul Eggert
2024-01-21  3:38     ` Po Lu
2024-01-21  4:04       ` Paul Eggert
2024-01-21  5:11         ` Po Lu [this message]
2024-01-21 16:54   ` Bruno Haible

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=87mssztgm8.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).