From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.utahime.jp (gate.utahime.jp [183.180.29.210]) by sourceware.org (Postfix) with ESMTPS id 7962A384B0C1 for ; Tue, 23 Jun 2020 23:31:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 7962A384B0C1 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=utahime.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=yasu@utahime.org Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gate.utahime.jp (Postfix) with ESMTPS id 3B95C6C6C for ; Wed, 24 Jun 2020 08:31:06 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=utahime.org; s=maybe2019112701; t=1592955066; bh=BOI428tuxf77TbxYAaQBRIjm85zGVfddHKNsqp8evzY=; h=Date:To:Subject:From:In-Reply-To:References; b=SYbW9hmwXjzsGXOjf1mejGafCWAKBfwT38dLZZHIhiqxUb15Lf93TcO2f0J8Por00 odUJ0xriUuHvDJHeWZ+Uk65I+MIgvaK9IpBA5KZfOkTgBqJyDTepForZ0zlFOVTkaF 1/y5iHhIbNKoxNvqtw1bjd1AmyDYi6a83iDQSKtJpgveBkfS6kkdJ/32lCaUJO5Tj+ JuLYXcQKq68nk8yKcpFxM8HqrBWD64og97Yze+v3eKF8YqFICicIymPClrB+fzmAhQ 750WPpMSK1plTGCbgHYHjrhG1nnF7iUyaZ7W5amUMYnbecCGWxsstldqJrdOnNCmmJ GIJCp7E7hth4Q== Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 40E6F56187; Wed, 24 Jun 2020 08:31:05 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at eastasia.home.utahime.org Date: Wed, 24 Jun 2020 08:20:25 +0900 (JST) Message-Id: <20200624.082025.347584623379706940.yasu@utahime.org> To: cygwin-apps@cygwin.com Subject: Re: zsh 5.8: configure fails only on 32bit From: Yasuhiro KIMURA In-Reply-To: <87lfkreckq.fsf@Otto.invalid> <23ce470a-9e82-612e-4208-d3e971080fa8@gmail.com> References: <20200613.060556.1408580419815246249.yasu@utahime.org> <87lfkreckq.fsf@Otto.invalid> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_ASCII_DIVIDERS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jun 2020 23:31:12 -0000 Thank you for reply, and sorry for late response. From: ASSI Subject: Re: zsh 5.8: configure fails only on 32bit Date: Sat, 13 Jun 2020 07:53:25 +0200 > 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. I tried what you say with newly clean installed 64bit Windows 10 Pro 1909. But problem still happens. From: Marco Atzeri via Cygwin-apps Subject: Re: zsh 5.8: configure fails only on 32bit Date: Sat, 13 Jun 2020 08:18:56 +0200 > 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 yasu@rolling[1070]% cygcheck -c cygwin mintty Cygwin Package Information Package Version Status cygwin 3.1.5-1 OK mintty 3.2.0-1 OK yasu@rolling[1071]% And after number of trials and errors I add following definition of src_compile function to zsh.cygport. ---------------------------------------------------------------------- src_compile() { cd ${S} cygautoreconf cd ${B} dash ${S}/configure --srcdir=${S} --prefix=$(__host_prefix) --exec-prefix=$(__host_prefix) --localstatedir=$(__host_localstatedir) --sysconfdir=$(__host_sysconfdir) --infodir=$(__host_prefix)/share/info --mandir=$(__host_prefix)/share/man -C --enable-function-subdirs --enable-gdbm --enable-multibyte --enable-pcre --enable-zsh-secure-free || error "configure failed" cygmake } ---------------------------------------------------------------------- This is same as default definition except that dash is used to interpret configure script. And with it build succeeded on 32bit Cygwin console. So It seems I hit bug of bash that only happens under very limited conditions. And I'm wondering if I should investigate the problem further or accept adding the function definition as a workaround. --- Yasuhiro KIMURA