From: Paul Eggert <eggert@cs.ucla.edu>
To: Lucy Phipps <landfillbaby69@gmail.com>
Cc: Gnulib bugs <bug-gnulib@gnu.org>
Subject: Re: #include <stdio.h> on Android clang causes an error
Date: Thu, 9 Sep 2021 00:12:06 -0700 [thread overview]
Message-ID: <71d4e51e-7a01-edaf-d1fe-3d9cb8c923b5@cs.ucla.edu> (raw)
In-Reply-To: <CAGOd_F8nUqQr5jDceLnhZDXc4kFZKNZpYQhOYeR02HJ4PAoX9Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
Your latest report helped me find another portability problem.
Ironically, a compatibility feature in Android API 23 intended to make
it easier porting GNU software by assuming the GNU API for strerror_r,
collided with a compatibility feature in Gnulib intended to make it
easier to port GNU software by assuming the POSIX API for strerror_r.
I installed a Gnulib patch to fix that (you should have received email a
few hours ago), and am attaching a revised gzip tarball. Please give it
a try.
Thanks again for these reports. They should help make it easier to run
several GNU programs on Android, not just gzip.
[-- Attachment #2: gzip-1.11.3-7c35.tar.xz --]
[-- Type: application/x-xz, Size: 804640 bytes --]
next prev parent reply other threads:[~2021-09-09 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 13:11 #include <stdio.h> on Android clang causes an error Lucy Phipps
2021-09-07 13:16 ` Lucy Phipps
2021-09-07 13:18 ` Lucy Phipps
2021-09-08 6:49 ` Paul Eggert
2021-09-08 10:45 ` Lucy Phipps
2021-09-08 16:55 ` Paul Eggert
2021-09-08 17:30 ` Lucy Phipps
2021-09-08 18:52 ` Lucy Phipps
2021-09-09 7:12 ` Paul Eggert [this message]
[not found] ` <CAGOd_F-fW-dkWihAgYUV96iNq7aMkLO+PsFvC9YvGzD+--bE3g@mail.gmail.com>
2021-09-09 10:25 ` Fwd: " Lucy Phipps
2021-09-09 11:08 ` Jim Meyering
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=71d4e51e-7a01-edaf-d1fe-3d9cb8c923b5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=landfillbaby69@gmail.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).