|
From: | Angelo Graziosi |
Subject: | Re: Build failure for Emacs master |
Date: | Tue, 19 Apr 2016 23:18:14 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
Il 19/04/2016 16:39, Eli Zaretskii ha scritto:
From: Angelo Graziosi <address@hidden> Date: Tue, 19 Apr 2016 11:58:57 +0200 I just noticed the following message about SED while configuring (it was there also in my previous builds) ./autogen.sh PKG_CONFIG_PATH=/mingw64/lib/pkgconfig ./configure --without-imagemagick [...] checking the archiver (ar) interface... ar checking for ar... (cached) ar checking for ranlib... ranlib checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking whether gcc -I ./nt/inc accepts -g3 -O2... yes sed: can't read conftest.c: No such file or directoryDoesn't happen here.
I image you are using a git check out as source, instead I am using the tar-ball http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-master.tar.gz. The cause of that SED failure seems the omission of "--enable-gcc-warnings=no" option. Indeed when I use
PKG_CONFIG_PATH=/mingw64/lib/pkgconfig ./configure --without-imagemagick --enable-gcc-warnings=no
the output is [...] checking for ranlib... ranlib checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... 64 checking whether gcc -I ./nt/inc accepts -g3 -O2... yes checking whether the compiler is clang... no checking whether C compiler handles -Werror -Wunknown-warning-option... no checking whether make supports nested variables... (cached) yes [...] No SED failure.Now all this seems strange because out of git check out, the option "--enable-gcc-warnings=no" should be enabled by default, if I understand some recent commit about it.. (It is YES, by default, in git check out, i think).
Maybe Paul has some idea about this.. Ciao, Angelo.
[Prev in Thread] | Current Thread | [Next in Thread] |