On 9/10/2009 09:59, Matthew Talbert wrote: >> Use 'svn export include /mypath/x86_64-w64-mingw32/include'. It will >> create the missing directory and copy the headers without the svn >> metadata. The metadata is in a .svn subdirectory in each directory you >> checkout via svn. > > 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. >> >>>> Maybe the wrong binutils got called, check your $PATH, make sure >>>> /opt/w64/bin is in it. >>> >>> Yes, /opt/w64/bin is in it. I've done this manually as well and it has >>> the same problem. >>> >> >> Use 'x86_64-w64-mingw32-gcc -print-prog-name=as', to find out where its >> invoking as. > > /opt/w64/bin/x86_64-w64-mingw32-gcc -print-prog-name=as > as > > I don't even have a x86_64....as. Should I? > According to your build script, you should have cross binutils already installed, -print-prog-name=as is to make sure it is calling the correct cross binutils. Do post the output, thanks. ------------------------------------------------------------------------------ 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
