X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=BAYES_00,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Vadim Zeitlin Subject: Re: m4 1.4.16-1 doesn't seem to work Date: Fri, 17 Jun 2011 17:16:02 +0000 (UTC) Lines: 37 Message-ID: References: <19921 DOT 30753 DOT 62000 DOT 974121 AT gargle DOT gargle DOT HOWL> <4DD293E4 DOT 2070407 AT redhat DOT com> <19922 DOT 61962 DOT 640000 DOT 987645 AT gargle DOT gargle DOT HOWL> <4DD2F7C1 DOT 1010205 AT redhat DOT com> <19922 DOT 64949 DOT 62000 DOT 98452 AT gargle DOT gargle DOT HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Uday S Reddy cs.bham.ac.uk> writes: > Eric Blake writes: > > > Odd; that says all your dlls are in place. The only other thing that I > > can suspect is that you have an incomplete dll, where you are missing a > > required entry point (perhaps you are running too old of a > > cygwin1.dll?). What is $? after the failed m4? Also, can you try > > opening up a cmd window, and running m4 from there, to see if you get a > > useful popup box? (running under a cygwin shell intentionally suppresses > > dll link error popup boxes) > > Indeed, you were right to suspect the dll. Reinstalling it cured the > problem. Sorry to revive a relatively old thread but I have the same problem as Uday except that I couldn't fix it. To summarize: 1. After a routine Cygwin upgrade m4 stopped working, it exits with $?=127 without any messages, even when ran from cmd.exe and not Cygwin prompt. 2. Reinstalling m4 1.4.16 didn't change anything. 3. Rolling back to 1.4.15 fixed the problem and m4 runs ok now. 4. Re-upgarding to 1.4.16 reintroduced the same problem so it wasn't just a bad upgrade or something like that. The output of cygcheck is the same for 1.4.15 and 1.4.16. However the output of ldd is normal for 1.4.15 but ldd hangs with 1.4.16 with m4 child process running but not doing anything. So it seems to me that there is a real problem with m4 1.4.16. Unfortunately I don't know how to debug it further. For the moment I'm just going to stay with 1.4.15 but if anybody has any ideas for further tests I'd be glad to perform them and post the results. Regards, VZ -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple