--- Sab 14/3/09, Dave Korn  ha scritto:

> Da: Dave Korn 
> Oggetto: Re: [ANNOUNCEMENT] Updated: experimental package: gcc4-4.3.2-2
> A: cygwin@cygwin.com
> Data: Sabato 14 marzo 2009, 04:04
> Angelo Graziosi wrote:
> > Still continuing to test...
> > 
> > Marco Atzeri wrote:
> >> if I had ./test_program I see the output on the
> screen but
> >>
> >> ./test_program > test_output
> >> leave test_output empty.
> > 
> > If I build that tst case with:
> > 
> > gfortran-4 test_program.F -o test_program
> > 
> > then
> > 
> > $ ./test_program.exe
> > SUCCESS
> > 
> > $ ./test_program.exe > test_output
> > 
> > $ cat test_output
> > SUCCESS
> 
>   Hmm, doesn't work here.  1.5 or 1.7?  This
> is 1.7:
> 
> ad...@ubik /tmp/fortran/hw
> $ cat hw.F
>       program main
>       WRITE(*,*) 
>    'SUCCESS'
>       end
> 
> ad...@ubik /tmp/fortran/hw
> $ gfortran-4 hw.F -o test_program
> 
> ad...@ubik /tmp/fortran/hw
> $ ./test_program.exe  > test_output
> 
> ad...@ubik /tmp/fortran/hw
> $ cat test_output

it seems a 1.7 specific fault.
On cygwin 1.5 it works; I never checked before :-( 

is it possible that Cygwin-1.7 is fooled by the not like-C
standard output ?

"GFORTRAN_STDOUT_UNIT—Unit number for standard output

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

http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gfortran/GFORTRAN_005fSTDOUT_005fUNIT.html#GFORTRAN_005fSTDOUT_005fUNIT

> 
>     cheers,
>       DaveK
> 

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/

Reply via email to