bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
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: Tue, 7 Sep 2021 23:49:03 -0700	[thread overview]
Message-ID: <51928d4b-8f66-c8d4-96e3-a899b130866d@cs.ucla.edu> (raw)
In-Reply-To: <CAGOd_F8gAmwg7OFp6Adr6gMx=d4cXKZ=HRFvba6g+F0MFU4Wfw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

On 9/7/21 6:11 AM, Lucy Phipps wrote:

> /home/builder/.termux-build/_cache/android-r21d-api-24-v5/bin/../sysroot/usr/include/malloc.h:168:37:
> error: unknown type name 'FILE'
> int malloc_info(int __must_be_zero, FILE* __fp) __INTRODUCED_IN(23);

Thank you for reporting this problem. I attempted to fix this in Gnulib 
(see my recent email to you, archived at 
<https://lists.gnu.org/r/bug-gnulib/2021-09/msg00024.html>). If you have 
the time, please give the fix a try. You can do that either by building 
from the latest Git version of gzip on Savannah, or (this is probably 
easier) by building from the attached tarball which I just now generated 
from Savannah.


[-- Attachment #2: gzip-1.11.2-aa5c.tar.xz --]
[-- Type: application/x-xz, Size: 807676 bytes --]

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

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=51928d4b-8f66-c8d4-96e3-a899b130866d@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).