bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
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 13:08:28 +0200	[thread overview]
Message-ID: <CA+8g5KGaPpHS6ttGoiXLrDCFdKqDej6m+uXCDXF4dtn4Znjz4A@mail.gmail.com> (raw)
In-Reply-To: <CAGOd_F8cMP2BcVErVZn9CynnO8a_iOhOaWpDirx6XPAstZ=fjQ@mail.gmail.com>

On Thu, Sep 9, 2021 at 12:27 PM Lucy Phipps <landfillbaby69@gmail.com> wrote:
>
> ---------- Forwarded message ---------
> From: Lucy Phipps <landfillbaby69@gmail.com>
> Date: Thu, Sep 9, 2021 at 11:25 AM
> Subject: Re: #include <stdio.h> on Android clang causes an error
> To: Paul Eggert <eggert@cs.ucla.edu>
>
> it works perfectly now! and yeah i was planning on applying this to
> several gnu packages :)
>
> On Thu, Sep 9, 2021 at 8:12 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
> >
> > 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.

Thanks indeed, to both of you.
This is good justification for making a new gzip release before long.


      reply	other threads:[~2021-09-09 11:08 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
     [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 [this message]

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=CA+8g5KGaPpHS6ttGoiXLrDCFdKqDej6m+uXCDXF4dtn4Znjz4A@mail.gmail.com \
    --to=jim@meyering.net \
    --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).