[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Android port
From: |
Eli Zaretskii |
Subject: |
Re: Android port |
Date: |
Sat, 05 Aug 2023 15:12:33 +0300 |
> From: Bruno Haible <bruno@clisp.org>
> Cc: Po Lu <luangruo@yahoo.com>, Paul Eggert <eggert@cs.ucla.edu>, Eli
> Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Date: Sat, 05 Aug 2023 13:20:31 +0200
>
> But from this error log:
>
> In file included from
> C:/msys64/tmp/emacs-bfbdf4eb892935536fc665d6cc986fd669364263/nt/inc/ms-w32.h:389,
> from ../src/conf_post.h:38,
> from ../src/config.h:3511,
> from printf.c:18:
> C:/msys64/mingw64/include/stdio.h:379:5: note: previous definition of
> 'printf' with type 'int(const char *, ...)'
>
> it seems that nt/inc/ms-w32.h directly includes <stdio.h> from mingw, without
> the interposed lib/stdio.h.
>
> Do you have a lib/stdio.h in your build tree?
The MinGW build omits building the Gnulib's stdio module. We did that
since 2017. The exact reasons are probably lost in time, but I can
assure you they were real, and I wouldn't want to reintroduce them for
this particular reason.
Since the *printf family doesn't need to be replaced in the Emacs
build on MS-Windows, I'd rather we understood why the above causes
compilation errors. Aren't Gnulib replacements for *printf functions
supposed to have prototypes compatible to the MinGW headers?
- Re: Android port, (continued)
- Re: Android port, Eli Zaretskii, 2023/08/04
- Re: Android port, Po Lu, 2023/08/04
- Re: Android port, Eli Zaretskii, 2023/08/05
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Angelo Graziosi, 2023/08/05
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Bruno Haible, 2023/08/05
- Re: Android port, Angelo Graziosi, 2023/08/05
- Re: Android port, Bruno Haible, 2023/08/05
- Re: Android port, Angelo Graziosi, 2023/08/05
- Re: Android port,
Eli Zaretskii <=
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Eli Zaretskii, 2023/08/05
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Bruno Haible, 2023/08/05
- Re: Android port, Eli Zaretskii, 2023/08/05
- Re: Android port, Bruno Haible, 2023/08/05
- Re: Android port, Eli Zaretskii, 2023/08/05
- Re: Android port, Po Lu, 2023/08/05
- Re: Android port, Eli Zaretskii, 2023/08/05