On 2013-10-3 9:50, asmwarrior wrote: > I'm not sure the failure reason of detecting expat library in gdb. OK, I find the reason.
There is another GCC in my system's PATH variable. Though the mouted /mingw has the high precedence in the PATH, but the configure script wrongly detect gcc in "another GCC", not the one mouted /mingw. The reason is configure script first try to detect mingw32-gcc.exe, secondly gcc.exe. But x32-4.8.1-posix-dwarf-rev5\mingw32\bin does not have mingw32-gcc.exe, it has either gcc.exe and i686-w64-mingw32-gcc-4.8.1.exe. So, the mingw32-gcc.exe in "another GCC" was detected and used. After fixing the PATH, gdb build successfully now. I'm sorry about the noise in this maillist. Yuanhui Zhang ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
