From: Corinna Vinschen <vinschen@redhat.com>
To: Alexey Lapshin <alexey.lapshin@espressif.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>,
Alexey Gerenkov <alexey.gerenkov@espressif.com>,
Ivan Grokhotkov <ivan@espressif.com>,
Anton Maklakov <anton.maklakov@espressif.com>
Subject: Re: [PATCH] libc: fix fropen/fwopen compile warnings
Date: Wed, 7 Dec 2022 13:23:14 +0100 [thread overview]
Message-ID: <Y5CFsmUu18XvEm6F@calimero.vinschen.de> (raw)
In-Reply-To: <7df8cf98f3652657eb0ff11565a8597af4e1e004.camel@espressif.com>
Hi Alexey,
On Dec 7 10:59, Alexey Lapshin wrote:
> This patch fixes warnings that appears when compiling:
>
>
> #define fwopen(__cookie,__fn) funopen(__cookie, (int (*)())0, __fn,
> (fpos_t (*)())0, (int (*)())0)
> Expands to:
>
> funopen(__null, (int (*)())0, &app_printf, (fpos_t (*)())0, (int
> (*)())0)
> argument of type "int (*)()" is incompatible with parameter of type
> "int (*)(void *__cookie, char *__buf, int __n)"C/C++(167)
> invalid conversion from 'fpos_t (*)()' {aka 'long int (*)()'} to
> 'fpos_t (*)(void*, fpos_t, int)' {aka 'long int (*)(void*,
>
> Discussion is here:
> https://github.com/espressif/arduino-esp32/issues/7407
Pushed.
Thanks,
Corinna
prev parent reply other threads:[~2022-12-07 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 10:59 Alexey Lapshin
2022-12-07 12:23 ` Corinna Vinschen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5CFsmUu18XvEm6F@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=alexey.gerenkov@espressif.com \
--cc=alexey.lapshin@espressif.com \
--cc=anton.maklakov@espressif.com \
--cc=ivan@espressif.com \
--cc=newlib@sourceware.org \
/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).