X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: octave compiled with gcc-3.4.4-2 - error messages during make check Date: Mon, 21 Aug 2006 10:16:03 +0100 Message-ID: <032801c6c502$6d0246b0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20060819222743.61809.qmail@web51504.mail.yahoo.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On 19 August 2006 23:28, James R. Phillips wrote: > I've built a test version of octave 2.1.73 on cygwin using the experimental > gcc-3.4.4-2 compiler. Thanks to Brian Dessent for pointing out a packaging > problem with the compiler and a workaround: > http://www.cygwin.com/ml/cygwin/2006-07/msg00620.html . Thanks for helping test the new compiler package! > The build is successful, but several of the tests executed during "make > check" issue error messages like the following: > > Running > /home/dad/sources/octave/octave-2.1.73/test/octave.test/quad/quad.exp ... > 102 [main] octave 1252 fork: child -1 - died waiting for longjmp before > initialization, retry 0, exit code > 0x80, errno 11 > > Interestingly, none of these tests actually fail in the summary report. > > The only hits I get with Google on this error message ["died waiting for > longjmp before initialization, retry 0"] relate to relatively recent issues > with the cygwin dll. I'm not sure how to classify this issue, i.e. whether > it is a cygwin issue, a compiler issue, or an octave issue. Also I'm not > sure how serious it is, since the tests it occurred on appeared to complete > successfully. > > Any help with analysis of these questions would be appreciated. Change one parameter at a time. Keep all others constant. See what changes. First thing would be to experiment with a few different versions of the cygwin dll, including the most recent snapshot. Re-run "make check" in the exact same object dir without rebuilding the application. Then, keeping the dll constant, try rolling your gcc install back to 3.4.4-1, building in a fresh object dir, and running make check there. Please let us know what results you get. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/