[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Current trunk is broken for MinGW, patches included
From: |
Gavin Smith |
Subject: |
Re: Current trunk is broken for MinGW, patches included |
Date: |
Thu, 25 Dec 2014 17:33:59 +0000 |
On Wed, Dec 24, 2014 at 5:41 PM, Eli Zaretskii <address@hidden> wrote:
> In addition, there are non-fatal warnings: libiconv routines are
> called with 'char **' arguments where the functions expect to get a
> 'const char **' argument, and there's one case of conflicting
> prototypes in pcterm.c. Patch for the latter is below; as for the
> iconv problem, I'm unsure how best to solve this, since I don't
> understand why the code doesn't use the correct types -- perhaps
> because non-GNU implementations of libiconv need that?
Which functions are giving warnings? All the documentation I have
looked at for "iconv" doesn't show "const" for any of the arguments.
- Current trunk is broken for MinGW, patches included, Eli Zaretskii, 2014/12/24
- Re: Current trunk is broken for MinGW, patches included, Gavin Smith, 2014/12/24
- Re: Current trunk is broken for MinGW, patches included, Gavin Smith, 2014/12/25
- Re: Current trunk is broken for MinGW, patches included,
Gavin Smith <=
- Re: Current trunk is broken for MinGW, patches included, Eli Zaretskii, 2014/12/25
- Re: Current trunk is broken for MinGW, patches included, Gavin Smith, 2014/12/28
- Re: Current trunk is broken for MinGW, patches included, Eli Zaretskii, 2014/12/28
- Re: Current trunk is broken for MinGW, patches included, Werner LEMBERG, 2014/12/28
- Re: Current trunk is broken for MinGW, patches included, Eli Zaretskii, 2014/12/29