Re: zsh 5.8: configure fails only on 32bit

[Marco Atzeri <marco.atzeri@gmail.com>]

On 12.06.2020 23:05, Yasuhiro KIMURA wrote:
> Hello,
> 
> I'm trying to update zsh package to its latest version 5.8. Version
> 5.5.1-1 still uses custom build shell script. So I migrated to use
> cygport. Attached files are .cygport file and patches. I blieve all
> customizations and modifications of 5.5.1-1 are included. But
> currently there is one problem.
> 
> On 64bit console 'cygport zsh.cygport all' completes successfully. But
> on 32bit console it fails with configure error as following.
> 
> ----------------------------------------------------------------------
> checking for /dev/fd filesystem... /proc/self/fd
> checking for RFS superroot directory... no
> checking whether we should use the native getcwd... no
> checking whether getcwd calls malloc to allocate memory... yes
> checking for setproctitle... no
> checking for library containing setproctitle... no
> checking for NIS... no
> checking for NIS+... no
> checking for utmp file... /var/run/utmp
> checking for wtmp file... no
> checking for utmpx file... no
> checking for wtmpx file... no
> checking for brk() prototype in <unistd.h>... no
> checking for sbrk() prototype in <unistd.h>... yes
> checking for mknod prototype in <sys/stat.h>... yes
> checking for ioctl prototype in <unistd.h> or <termios.h>... no
> checking for ioctl prototype in <sys/ioctl.h>... yes
> checking if named FIFOs work... yes
> checking if link() works... yes
> checking if kill(pid, 0) returns ESRCH correctly... yes
> checking if POSIX sigsuspend() works... yes
> checking if tcsetpgrp() actually works... yes
> checking if getpwnam() is faked... no
> checking base type of the third argument to accept... socklen_t
> checking if your system has /dev/ptmx... yes
> make: *** No targets specified and no makefile found.  Stop.
> *** ERROR: make failed
> yasu@rolling[1301]%
> ----------------------------------------------------------------------
> 
> According to config.log configure script is executed with following options.
> 
> /cygdrive/c/Users/yasu/Work/Cygwin/zsh/zsh.cygwin/zsh-5.8-1.i686/src/zsh-5.8/configure --srcdir=/cygdrive/c/Users/yasu/Work/Cygwin/zsh/zsh.cygwin/zsh-5.8-1.i686/src/zsh-5.8 --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/zsh --htmldir=/usr/share/doc/zsh/html -C --enable-function-subdirs --enable-gdbm --enable-multibyte --enable-pcre --enable-zsh-secure-free
> 
> So I executed it directly from command line. Then it completed without
> any error.
> 
> Why such difference happens? Does cygconf function do something other
> than executing configure script?
> 

what cygwin version and terminal are you using ?
I saw a similar problem in the past

https://sourceware.org/pipermail/cygwin/2020-April/244363.html
https://sourceware.org/pipermail/cygwin-apps/2020-May/040107.html

and it went away with a recent cygwin

> Best Regards.
> 
> ---
> Yasuhiro KIMURA
> 

Regards
Marco