X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_83 X-Spam-Check-By: sourceware.org Message-ID: <64736.91417.qm@web25006.mail.ukl.yahoo.com> Date: Sat, 14 Mar 2009 07:31:41 +0000 (GMT) From: Marco Atzeri Subject: Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2 To: cygwin AT cygwin DOT com, Dave Korn MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 --- Sab 14/3/09, Dave Korn ha scritto: > Da: Dave Korn=20 > Oggetto: Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2 > A:=20 > Data: Sabato 14 marzo 2009, 07:56 > Marco Atzeri wrote: >=20 > > it seems a 1.7 specific fault. On cygwin 1.5 it works; > I never checked > > before :-( >=20 > =C2=A0 Odd!=C2=A0 It fails for me on both.=C2=A0 (You did > update gcc-4 on *both* your > installations, right?) >=20 yes $ uname -a CYGWIN_NT-5.1 ITQMOZCAS2NB007 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin $ cygcheck -c -d |grep fortran gcc4-fortran 4.3.2-2 libgfortran3 4.3.2-2 $cygcheck ./conftest-15.exe .\conftest-15.exe C:\cygwin\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll C:\cygwin\bin\cyggcc_s-1.dll C:\cygwin\bin\cyggfortran-3.dll $ ./conftest-15.exe > conftest.out ; cat conftest.out=20 SUCCESS $ uname -a=20 CYGWIN_NT-5.1 ITQMOZCAS2NB007 1.7.0(0.206/5/3) 2009-03-11 14:08 i686 Cygwin cygcheck -c -d |grep fortran gcc4-fortran 4.3.2-2 libgfortran3 4.3.2-2 $ cygcheck ./conftest-17.exe C:\cygwin2\pub\programs\fortran\conftest-17.exe C:\cygwin2\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll C:\cygwin2\bin\cyggcc_s-1.dll C:\cygwin2\bin\cyggfortran-3.dll $ ./conftest-17.exe > conftest.out ; cat conftest.out=20 So I can reproduce it only on cygwin-1.7. > > is it possible that Cygwin-1.7 is fooled by the not > like-C standard output > > ? > >=20 > > "GFORTRAN_STDOUT_UNIT=E2=80=94Unit number for standard > output > >=20 > > This environment variable can be used to select the > unit number > > preconnected to standard output. This must be a > positive integer. The > > default value is 6. " >=20 > =C2=A0 I'm not sure.=C2=A0 From what I've studied so far of > libgfortran/io, I think the > fortran "unit" numbers are mapped to, rather than directly > equivalent to, unix > fds.=C2=A0 It might be a libgfortran bug, or it may even > not; there could be some > interaction in the cygwin dll between DLL unload and stdio > shutdown during the > exit sequence that fails to flush the stream properly, for > example.=C2=A0 Still > investigating. >=20 > =C2=A0 =C2=A0 cheers, > =C2=A0 =C2=A0 =C2=A0 DaveK >=20 Regards Marco -- 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/