On 9/7/2010 09:37, Xiaofan Chen wrote: > On Tue, Sep 7, 2010 at 8:12 AM, JonY<[email protected]> wrote: >>> My problem is that libtool was pointing to lib64 directory in the 64bit >>> cross build (under Linux or 32bit Windows) cases. I need to check again >>> under 32bit Win 7 with TDM. >>> >>> I just checked under Windows 7 64bit and TDM64 is okay there >>> without the lib64 directory when building libusb-1.0 Windows >>> backend. >>> >> Can you please show your gcc configure line with gcc -v? > > I have different installation of MinGW-w64 (from MinGW-w64 Sourceforge > for Linux and Windows, from http://www.drangon.org/mingw/ for > Linux and 64bit Windows, and TDM64 for 32/64bit Windows). I need > to check again which is the problematic ones and report back > the configure line of "gcc -v". > > You can see that I were trying to find a proper MinGW-w64 binary > distribution. Last time WPG-System64 was the one. But then it > is not maintained any more and no longer compatible with latest > MinGW-w64. It seems to me TDM64 is the new one. > > I initially preferred to get the "proper" one from MinGW-w64 site, > especially one that works under 32bit Windows to build 64bit > target (the mingw-w64-bin_i686-mingw ones). Unfortunately it > seems to me the latest version is sezero's private build dated > 20100711. The latest automatic build is dated 20100702. > I do not quite understand that why i686_mingw target is > less important than say the Cygwin target. Anyway, TDM64 > seems to fill the void now. >
Buildbot is failing, specifically makeinfo parts in gcc when msys is used, before that, mpc configure.ac was being braindead. So yeah, failure after failure on MSYS. Perhaps we can get rid of MSYS buildbot completely and switch to linux or Cygwin type of Canadian cross build. We are in the progress of debugging it. Join the irc channel, (NightStrike) NS2 and Mook is likely to know about the issue. > The other main problem with current MinGW-w64 is the ddk > header. I am one of the admins of libusb-win32 project > (mainly on the testing and supporting side), right now it > is not possible to build the driver part using MinGW-w64. > MinGW.org 32bit compiler is okay. > You could report the problems and we'll try to fix them on our end. >> Check also if mingw and x86_64-w64-mingw32 are linked (or identical to each >> other). This "mingw" directory is equivalent to usr when sysroot is in use. > > I am quite sure they are linked. > OK. Please post the gcc configure line, along with the failing libtool command and its error/warnings. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
