>> >> Perhaps I should have mentioned earlier, I'm compiling from the 4.4.0 >> release, not from svn. Still, the directions are wrong, yes? (They >> neglect the trailing "include" directory, so you would be copying the >> contents of include to /mypath/x86_64-mingw32). >> > > Hi, > I was referring to the svn checkout of the mingw-w64 headers, not gcc. > Just export the headers directory instead of copying it. > > The svn metadata shouldn't be there, accidentally updating the installed > headers by svn without first checking for ABI change is hazardous to > your toolchain.
I'm using this https://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Release%20for%20GCC%204.4.0/mingw-w64-src-4.4.0-1.tar.bz2/download which includes the mingw-w64 headers. So there is no svn metadata involved as far as I know. Matthew ------------------------------------------------------------------------------ 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 Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
