X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_BG,TW_QR,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20110326160529.GI24762@calimero.vinschen.de>
References: <AANLkTikw5F9-M=4Cw9HuGBFUoF2uYUWyOgeosD5STUSw AT mail DOT gmail DOT com>	<20110326094551 DOT GF24762 AT calimero DOT vinschen DOT de>	<AANLkTinv0j=WGG8g3y2AMg2Qm275BAB9kW8tw37bLcdf AT mail DOT gmail DOT com>	<20110326160529 DOT GI24762 AT calimero DOT vinschen DOT de>
Date: Sat, 26 Mar 2011 19:18:05 +0100
Message-ID: <AANLkTimVvXZE802PeLUWP_eLxL8jac7XVNTg5D+NhDf4@mail.gmail.com>
Subject: Re: libgfortran3 respin : status and problem
From: marco atzeri <marco DOT atzeri AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Sat, Mar 26, 2011 at 5:05 PM, Corinna Vinschen  wrote:
> On Mar 26 11:33, marco atzeri wrote:
>> On Sat, Mar 26, 2011 at 10:45 AM, Corinna Vinschen =A0wrote:
>> > So, what you see is a supposedly endless stream of calls to the write
>> > function. =A0Usually, if an error occurs, you would also see an error
>> > message. =A0The only reason you don't see it is if an error already
>> > occured in an earlier call to write. =A0The important would be prior to
>> > the endless loop then. =A0Maybe the testcase doesn't check for errors?
>>
>> the test case is a normal Fortran program that call numerical functions =
and
>> print output with a really standard "write" command, nothing fancy.
>> It used to work fine with previous libgfortran3-4.3.4-3 and cygwin-1.7.7
>
> What about current libgfortran3 and cygwin 1.7.7? =A0What about previous
> libgfortran3 and cygwin 1.7.8?

I will make all the test as soon I built a simpler test case involving
only libgfortran3 and cygwin .
Currently qrupdate require lapack and lapack 3.2.2-1 was broken by the
libgfortran3 update.

Today I have
cygwin-1.7.7 , libgfortran3-4.3.4-3, lapack-3.2.2-1,
qrupdate-qrupdate-1.1.0-1 fine
cygwin-1.7.8 , libgfortran3-4.3.4-4, lapack-3.2.2-2,
qrupdate-qrupdate-1.1.1-1 broken (as also octave3.4.0-3)

>> The full source is here, and it is a very tiny lib
>> http://matzeri.altervista.org/cygwin-1.7/qrupdate/
>
> Yes, well, are you going to debug this problem?

yes but very slowly, my real job take me real busy and I have little spare =
time.

> Corinna
>

Regards
Marco

--
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