From: Ozkan S. <se...@gm...> - 2009-08-21 07:43:08
|
On Fri, Aug 21, 2009 at 10:24 AM, Kai Tietz<kti...@go...> wrote: > 2009/8/21 t6...@gm... <t6...@gm...>: >> Hello, >> I filed a bug report at gcc bug tracker >> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41136 >> Is anyone encountering this bug and is there any possible workaround ? >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Mingw-w64-public mailing list >> Min...@li... >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public >> > > Hello, > > thank you for reporting this. Please report such kind of failures to > mingw-w64 project's bug tracker first. This looks not as a gcc bug > itself, it seems to be more reasoned by other issues possibly reasoned > by our runtime. > > Please describe also the environment you are using to build the native > compiler, the date of runtime headers and crt you are using, and the > binutils version you are using. > > Regards, > Kai This happens because the autotools idiocy decides that LFS is not available and _GLIBCXX_USE_LFS is left undefined which is the first issue, it falls back to fstat instead of fstat64 and fstat wraps onto fstat64i32. This is actually a GCC bug, IMO. The second issue is that fstat64i32 is in _fstat64i32.c but fstat() being defined as an inline wrapping around it in sys/stat.h is marked __MINGW_ATTRIB_NO_OPTIMIZE The no-optimize maybe causing an issue here ?. -- Ozkan |