From: Patrick H. <pa...@13...> - 2007-08-29 21:58:13
|
NightStrike wrote: > On 8/29/07, Patrick Hartling <pa...@13...> wrote: >> Is there a known good version of GNU Binutils to use in the 64-bit >> cross-compiler environment for MinGW? I was using a snapshot from June= 29, >> 2007, and this morning, I updated to the latest version from their CVS= >> repository. For some reason, x86_64-pc-mingw32-ar.exe is generating ba= d .a >> files now. I don't know if I did something wrong in building Binutils = or if >> this is a Binutils bug. However, if there is a version of the software= that >> is known to be in good shape, I will revert to it. >=20 > If there's an issue with ar not working, file a bug report on it. >=20 > For what it's worth, the latest version works ok for me. What are > your configure options, and what are you trying to pass into ar? I ran the Binutils configure script with the option --target=3Dx86_64-pc-mingw32 and used the MinGW version of GCC 3.4.5 to b= uild it. When I am using this version of ar, it is used in the following way: x86_64-pc-mingw32-ar rc file.a obj1.o obj2.o ... x86_64-pc-mingw32-ranlib file.a x86_64-pc-mingw32-ranlib complains that file.a is not in a recognized format, as does x86_64-pc-mingw32-nm. If I change the build to use the regular 32-bit MinGW ar and ranlib, it archives the 64-bit object files i= n a format that is recognizable. -Patrick --=20 Patrick L. Hartling VP Engineering, Infiscape Corp. http://www.infiscape.com/ |