X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0CA9C3857016 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Subject: Re: Just updated cygutils and cygstart no longer works To: cygwin AT cygwin DOT com References: <1318f7eb-abf0-bcc9-c040-3edc71602d6c AT maxrnd DOT com> <20210814105405 DOT 50c21fe7f450ca23dc774ebe AT nifty DOT ne DOT jp> From: Mark Geisert Message-ID: <831d3b59-0205-1d13-e5a0-2af494b7180c@maxrnd.com> Date: Fri, 13 Aug 2021 20:17:58 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, BODY_8BITS, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 17E3Isqh003679 Brian Inglis wrote: > On 2021-08-13 19:54, Takashi Yano via Cygwin wrote: >> On Fri, 13 Aug 2021 15:20:40 -0700, Mark Geisert wrote: >>> Jay Abel via Cygwin wrote: >>>> On Fri, Aug 13, 2021 at 10:27 AM Jay Abel wrote: > >>>> Sorry, more information.  I'm running Windows 10, 64-bit, AMD. >>>> >>>> I've reverted cygutils back to 1.4.16-2 and the problem is resolved. > >>>>> Run cygstart with anything and no window opens.  I've tried URLS cygstart >>>>> http://www.cygwin.com, directories cygstart . and cygstart ./  as well as >>>>> pdf files cygstart example.pdf. >>>>> None of these seems to do anything anymore. > >>> I have the same setup as you but all seems well here.  With 1.4.16-3 installed all >>> four of your testcases work for me.  I don't know what to suggest. >>> When you have a chance, what does 'echo $?' say at the prompt after cygstart >>> finishes one of your testcases?  0 means successful, 1 (or something else) means >>> failure. > >> I have the same issue with cygstart in cygutils 1.4.16-3. >> "cygstart .; echo $?" says 0. >> This issue only happens in 64bit cygwin and cygstart in 32bit cygwin works. >> To look into this problem, I tried to build cygutils from source, >> however, it fails in the link stage of getclip with the error: >> /usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld: >> src/clip/getclip.o: in function `getclip': >> /usr/src/debug/cygutils-1.4.16-3/src/clip/getclip.c:431: undefined reference to >> `__imp_RtlUnicodeToUTF8N' >> It seems that -lntdll flag is required to build it. Doesn't this error >> happen in your environment? >> So I modified Makefile.am to: >> src_clip_getclip_LDADD              = -lpopt -lntdll >> src_clip_putclip_LDADD              = -lpopt -lntdll >> and tried to build again and succeeded. >> The cygstart built locally works fine. >> So I tried to debug cygstart using gdb and it says: >> Thread 1 received signal SIGILL, Illegal instruction. >> The disassembling result at $rip is: >> => 0x0000000100401c15 <+389>:   vmovdqa 0x18c3(%rip),%xmm0        # 0x1004034e0 >> This is a AVX instruction. >> My CPU is Core i7-870, which does not support AVX. >> Then I ran cygstart in another machine whose CPU is Core i7-4790 >> and it works without the issue. >> Conclusion: >> cygstart in cygutils 1.4.16-3 is compiled with AVX extentions, >> therefore it can not run in old machine. > > Any chance this could have been built with test gcc 11 using non-standard values > instead of defaults -march=x86-64/i686 -mtune=generic? No, gcc 10.2.0 was used with those defaults. ..mark -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple