http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50016
--- Comment #18 from xunxun <xunxun1982 at gmail dot com> 2011-10-20 06:49:19 UTC --- (In reply to comment #17) > Author: burnus > Date: Wed Oct 19 17:27:03 2011 > New Revision: 180199 > > URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180199 > Log: > 2011-10-19 Janne Blomqvist <j...@gcc.gnu.org> > Kai Tietz <kti...@redhat.com> > Tobias Burnus <bur...@net-b.de> > > PR fortran/50016 > * io/unix.h (flush_sync): Add new libgfortran-internal > * prototype. > * io/unix.c (flush_sync): New function, which calls sflush and > on MinGW(-w64) also _commit. > (flush_all_units, flush_all_units_1): Replace sflush/_commit by > flush_sync. > * io/file_pos.c (st_flush): Replace sflush/_commit by > * flush_sync. > * io/intrinsics.c (flush_i4, flush_i8): Ditto. > > > Modified: > branches/gcc-4_6-branch/libgfortran/ChangeLog > branches/gcc-4_6-branch/libgfortran/io/file_pos.c > branches/gcc-4_6-branch/libgfortran/io/intrinsics.c > branches/gcc-4_6-branch/libgfortran/io/unix.c > branches/gcc-4_6-branch/libgfortran/io/unix.h Will the rev 180199 merge into gcc4.6.2 release? Because the first 4.6.2 RC doesn't contain the modify, gcc-4.6.2-RC-20111019 libgfortran build on mingw/mingw64 can cause: libtool: compile: i686-w64-mingw32-gcc -L/mingw/i686-w64-mingw32/lib -L/mingw/mingw/lib -isystem /mingw/i686-w64-mingw32/include -isystem /mingw/mingw/include -DHAVE_CONFIG_H -I. -I../.././libgfortran -iquote../.././libgfortran/io -I../.././libgfortran/../gcc -I../.././libgfortran/../gcc/config -I../.././libgfortran/../libquadmath -I../../host-i686-w64-mingw32/gcc -D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings -fcx-fortran-rules -ffunction-sections -fdata-sections -g -pipe -O2 -I/mingw/include -MT file_pos.lo -MD -MP -MF .deps/file_pos.Tpo -c ../.././libgfortran/io/file_pos.c -o file_pos.o ../.././libgfortran/io/file_pos.c: In function 'st_flush': ../.././libgfortran/io/file_pos.c:457:20: error: 'stream' has no member named 'fd' I would hope the next 4.6.2 RC or release fix the problem. Thanks.
