On 11/5/12, Ruben Van Boxem <[email protected]> wrote: > 2012/11/5 Václav Šmilauer <[email protected]> > >> Hi everybody, >> >> I was hitting the "File too large" error triggered by as.exe trying to >> write some files. I somehow managed to work around it by splitting >> compilation in smaller parts, by compiling without -g and/or with -Os. >> >> Why is it that a native 64bit compiler is hitting this 32bit limit? Is >> there a build which does not have this limitation? >> > > If the file size is a problem, this will only be fixed with large file > support (I think). But if not, I'm guessing your toolchain consists of > 32-bit executables (you can check by looking at the task manager and > looking for gcc.exe*32 or as.exe*32 which would be gcc.exe or as.exe if > they were 64-bit). > > My toolchains for 64-bit Windows are themselves built as 64-bit > executables, and my 32-bit to 64-bit toolchains are also linked with the > large-address-aware flag. You can find them here: > http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/ > > These allow more memory to be allocated, and perhaps also larger files to > be addressed. If these don't "fix" the issue, I guess the large file > support in trunk mingw-w64 could affect this in a positive way.
Is LFS support in trunk different than and/or improved against stable/v2.x?? > > Hope this helps, > > Ruben -- O.S. ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
