After 1bb0e177124d5d6661b72df6c7d848fb23639652
author Thorsten Behrens <thorsten.behrens@xxxxxxxxxxxxx>
2021-12-28 17:22:29 +0100
committer Thorsten Behrens <thorsten.behrens@xxxxxxxxxxxxx>
2021-12-28 21:14:58 +0100
commit 1bb0e177124d5d6661b72df6c7d848fb23639652 (patch)
tree 257fbb13364b2f5f565ed5d1ad7e859f8e3c096e
parent cfbcbb605dbaaea45dc9ac5ea792d72cb2f2c1bb (diff)
Fix autoconf>=2.70 gcc-wrapper breakage
Re-generated configure file gets confused & claims not finding C89-
compatible compiler for gcc-wrapper-building libassuan with msvc
underneath.
Work-around the problem by telling toolchain right off that this
_is_ a std c compliant compiler.
I confirm that it works now with last autoconf version retrieved on
Cygwin package manager.
Thank you Thorsten!
Julien
On 27/12/2021 22:07, Julien Nabet wrote:
On 27/12/2021 21:58, Hossein Nourikhah wrote:
Hello,
On 27.12.2021 18:46, Jan-Marek Glogowski wrote:
Am 27.12.21 um 18:30 schrieb Julien Nabet:
On Win10, I updated my local repo after some weeks and it fails with:
And you updated Cygwin...
checking how to run the C preprocessor...
C:/cygwin/home/serva/lode/dev/core/workdir/LinkTarget/Executable/gcc-wrapper.exe
-E
configure: error: No C-89 compiler found
make[1]: ***
[C:/cygwin/home/serva/lode/dev/core/external/libassuan/ExternalProject_libassuan.mk:26:
C:/cygwin/home/serva/lode/dev/core/workdir/ExternalProject/libassuan/build]
Error 1
make: *** [Makefile:291: build] Error 2
Cygwin updated the default to autoconf 2.70+. Workaround: uninstall
the autoconf2.7 package and install the autoconf2.5 (2.69) package and
downgrade the meta-package. AFAIK --disable-gpgmepp also works, but I
didn't test.
I have tested building LibreOffice using --disable-gpgmepp on Windows
10, Cygwin 3.3.3 and autoconf 2.71 using VS 2019 and it worked fine.
The two ways to fix this problem are now written down in the wiki:
https://wiki.documentfoundation.org/Development/BuildingOnWindows#Install_Cygwin_Requirements
Thank you Jan-Marek, I confirm downgrading autoconf worked!
Thank you Hossein too for having tested the other workaround and
updated the documentation.
Now I suppose the real fix will come from libassuan.
Julien
