zsh 5.8: configure fails only on 32bit

ASSI Stromeko@nexgo.de
Sat Jun 13 05:53:25 GMT 2020

Yasuhiro KIMURA writes:
> 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.

To me that indicates either BLODA interference or that you run into some
limit (e.g. on environment size or PATH length).

More generally I'd advise everyone to not build in your Windows user
directory (which Windows specially "protects" in various ways) and never
use any /cygdrive prefix while building packages (these are mounted with
posix=0 mount option by default).  If you have the option, use a
separate SSD for all of Cygwin and create a separate mount point for the
build directory that mounts with "posix=1,binary".  I haven't sprung for
full case sensitivity yet myself since that still entails mucking with
the registry more than I want to, but I've run into problems with that
once or twice (which I've worked around).  Install Cygwin into a
directory two levels down the root (i.e D:\Freeware\Cygwin) in order to
not get "special" treatment from Windows.  I have forgotten what the
exact problem was, but putting the Cygwin install directory directly
into the root triggered some BLODA several years ago.  Also if you use
Cygwin for yourself on that same machine it is better to have a separate
user account for building (I use a dedicated build machine).  Set
CYGWIN_NOWINPATH=1 in the system or user environment options of Windows
for the build user.  Be aware that some packages need to build or tested
with admin rights enabled (that's a whole 'nother reason to not use your
main account, as these days it shouldn't have admin rights at all),
which I generally have since I build via ssh.  Once in a while you'll
run into some test that fails until you aren't admin, in which case you
can use cygdrop.  Lastly, once you need to build GUI applications you
might want to be able to RDC into your build box, which means it should
have at least the "Professional" variant of Windows installed.

> Why such difference happens? Does cygconf function do something other
> than executing configure script?

You can run cygport with the --debug switch and it will give you more
details about what it does than you ever wanted to look at.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:

More information about the Cygwin-apps mailing list