Menu
▾
▴
Re: [Mingw-w64-public] rubenvb 4.7.1-2-release build
|
From: Ray D. <min...@gm...> - 2012-08-23 09:34:48
|
Interesting, my own build of jom (via mingw32 toolchain and my own Qt compile ages ago) has never failed to my knowledge: http://mingw-and-ndk.googlecode.com/files/jom.7z On Thu, Aug 23, 2012 at 9:52 AM, Loaden <lo...@gm...> wrote: > I know jom, it's only for nmake instead. > Some times, it's will faild for building. So I don't like it. > Qt is a complex system. > So, I prefer to use nmake for MSVC, and mingw32-make for MinGW, and make for > GCC. > B.T.W, I can build qt5 under Linux, use you cross mingw-w64, so, thanks you > very much! > Thank you great work! > 2012/8/23 Ruben Van Boxem <van...@gm...> >> >> 2012/8/23 Ruben Van Boxem <van...@gm...> >>> >>> 2012/8/23 Loaden <lo...@gm...> >>>> >>>> mingw32-make.exe problem after 4.7.0 ~ 4.7.1-2 and 4.6.3-1 >>>> When I build Qt5 using >>>> x86_64-w64-mingw32-gcc-4.6.3-release-win64_rubenvb.7z on Windows, It's works >>>> well! >>>> But the configure failed with 4.7.0 ~ 4.7.1-2 and 4.6.3-1 >>>> >>>> Failed Message: >>>>> >>>>> g++ -Wl,-subsystem,console -mthreads -o ../../configure.exe main.o >>>>> configureapp.o environment.o tools.o qarraydata.o qbytearray.o >>>>> qbytearraymatcher.o qhash.o qlist.o qlocale.o qlocale_win.o qlocale_tools.o >>>>> qvector.o qutfcodec.o qtextcodec.o qglobal.o qnumeric.o qbuffer.o >>>>> qdatastream.o qdir.o qdiriterator.o qfiledevice.o qfile.o qfileinfo.o >>>>> qabstractfileengine.o qfilesystementry.o qfilesystemengine.o >>>>> qfilesystemengine_win.o qfilesystemiterator_win.o qfsfileengine.o >>>>> qfsfileengine_win.o qfsfileengine_iterator.o qiodevice.o qtextstream.o >>>>> qlogging.o qtemporaryfile.o qsystemlibrary.o qbitarray.o qdatetime.o qmap.o >>>>> qregexp.o qstring.o qstringlist.o qvsnprintf.o qvariant.o qsystemerror.o >>>>> qmetatype.o qmalloc.o qxmlstream.o qxmlutils.o quuid.o qcryptographichash.o >>>>> registry.o -lole32 -ladvapi32 -luuid >>>>> g++: error: main.o: No such file or directory >>>>> g++: error: configureapp.o: No such file or directory >>>>> g++: error: environment.o: No such file or directory >>>>> g++: error: tools.o: No such file or directory >>>>> g++: error: qarraydata.o: No such file or directory >>>>> g++: error: qbytearray.o: No such file or directory >>>>> g++: error: qbytearraymatcher.o: No such file or directory >>>>> g++: error: qhash.o: No such file or directory >>>>> g++: error: qlist.o: No such file or directory >>>>> g++: error: qlocale.o: No such file or directory >>>>> g++: error: qlocale_win.o: No such file or directory >>>>> g++: error: qlocale_tools.o: No such file or directory >>>>> g++: error: qvector.o: No such file or directory >>>>> g++: error: qutfcodec.o: No such file or directory >>>>> g++: error: qtextcodec.o: No such file or directory >>>>> g++: error: qglobal.o: No such file or directory >>>>> g++: error: qnumeric.o: No such file or directory >>>>> g++: error: qbuffer.o: No such file or directory >>>>> g++: error: qdatastream.o: No such file or directory >>>>> g++: error: qdir.o: No such file or directory >>>>> g++: error: qdiriterator.o: No such file or directory >>>>> g++: error: qfiledevice.o: No such file or directory >>>>> g++: error: qfile.o: No such file or directory >>>>> g++: error: qfileinfo.o: No such file or directory >>>>> g++: error: qabstractfileengine.o: No such file or directory >>>>> g++: error: qfilesystementry.o: No such file or directory >>>>> g++: error: qfilesystemengine.o: No such file or directory >>>>> g++: error: qfilesystemengine_win.o: No such file or directory >>>>> g++: error: qfilesystemiterator_win.o: No such file or directory >>>>> g++: error: qfsfileengine.o: No such file or directory >>>>> g++: error: qfsfileengine_win.o: No such file or directory >>>>> g++: error: qfsfileengine_iterator.o: No such file or directory >>>>> g++: error: qiodevice.o: No such file or directory >>>>> g++: error: qtextstream.o: No such file or directory >>>>> g++: error: qlogging.o: No such file or directory >>>>> g++: error: qtemporaryfile.o: No such file or directory >>>>> g++: error: qbitarray.o: No such file or directory >>>>> g++: error: qdatetime.o: No such file or directory >>>>> g++: error: qmap.o: No such file or directory >>>>> g++: error: qregexp.o: No such file or directory >>>>> g++: error: qstring.o: No such file or directory >>>>> g++: error: qstringlist.o: No such file or directory >>>>> g++: error: qvsnprintf.o: No such file or directory >>>>> g++: error: qvariant.o: No such file or directory >>>>> g++: error: qsystemerror.o: No such file or directory >>>>> g++: error: qmetatype.o: No such file or directory >>>>> g++: error: qmalloc.o: No such file or directory >>>>> g++: error: qxmlstream.o: No such file or directory >>>>> g++: error: qxmlutils.o: No such file or directory >>>>> g++: error: qcryptographichash.o: No such file or directory >>>>> g++: error: registry.o: No such file or directory >>>>> mingw32-make: *** [../../configure.exe] Error 1 >>>>> *** qtbase/configure exited with non-zero status. >>>> >>>> >>>> If I copy the mingw32-make.exe from >>>> x86_64-w64-mingw32-gcc-4.6.3-release-win64_rubenvb.7z to >>>> x86_64-w64-mingw32-gcc-4.7.1-2-release-win64_rubenvb.7z, Then everything >>>> works well! >>>> Successful Message: >>>>> >>>>> g++ -Wl,-subsystem,console -mthreads -o ../../configure.exe main.o >>>>> configureapp.o environment.o tools.o qarraydata.o qbytearray.o >>>>> qbytearraymatcher.o qhash.o qlist.o qlocale.o qlocale_win.o qlocale_tools.o >>>>> qvector.o qutfcodec.o qtextcodec.o qglobal.o qnumeric.o qbuffer.o >>>>> qdatastream.o qdir.o qdiriterator.o qfiledevice.o qfile.o qfileinfo.o >>>>> qabstractfileengine.o qfilesystementry.o qfilesystemengine.o >>>>> qfilesystemengine_win.o qfilesystemiterator_win.o qfsfileengine.o >>>>> qfsfileengine_win.o qfsfileengine_iterator.o qiodevice.o qtextstream.o >>>>> qlogging.o qtemporaryfile.o qsystemlibrary.o qbitarray.o qdatetime.o qmap.o >>>>> qregexp.o qstring.o qstringlist.o qvsnprintf.o qvariant.o qsystemerror.o >>>>> qmetatype.o qmalloc.o qxmlstream.o qxmlutils.o quuid.o qcryptographichash.o >>>>> registry.o -lole32 -ladvapi32 -luuid >>>>> Preparing build tree... >>>>> Setting accessibility to NO >>>> >>>> >>>> So, It should a mingw32-make issue/bug/problem. >>>> Hope this can be solved. >>> >>> >>> Yes you are correct. >>> >>> Sezero has pointed this out to me on the MinGW-w64 forums that I seem to >>> have forgotten to apply a patch I previously applied to GNU Make 3.82. You >>> can at all times use this make build: >>> >>> http://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20%28Win64%20hosted%29/make/ >>> >>> so you wouldn't have to download and extract a whole toolchain. The fix >>> will be in the next build. Sorry about this, my own damn fault :) >>> >>> Ruben >>> >> >> That being said, for really building Qt (after configure), you should use >> their "jom" tool, which although written as an nmake clone, works great for >> Qt's qmake (and CMake's) Makefiles. Find it here: >> ftp://ftp.qt.nokia.com/jom/ >> >> Ruben >> >> >>> >>> >>>> >>>> >>>> 2012/8/17 Ruben Van Boxem <van...@gm...> >>>>> >>>>> Hi everyone, >>>>> >>>>> I kind of borked parts of my previous 4.7 release. I apologize again, >>>>> because I should have caught the problems reported before I uploaded the >>>>> stuff. These now include MinGW-w64 v2.0.6. >>>>> >>>>> I am in the process of uploading 4.7.1-2-release packages. I tested the >>>>> i686-win32 compiler, and it doesn't crash. I also verified the that the >>>>> 32-bit binaries are "--large-address-aware", although I provide 64-bit to >>>>> 32-bit cross-compilers. I built everything on Debian 6.0 stable, which >>>>> should mean it runs just about everywhere. Concretely: minimum Linux system >>>>> requirements are now: x86_64 and glibc >= 2.11. I tested on Debian and Arch >>>>> Linux, and on both systems the binaries now run fine. >>>>> >>>>> The mac build is postponed still. The new mac cross compiler has the >>>>> same issue as the one in Fedora. Both are unfortunately unable to build GCC. >>>>> >>>>> I will also be rebuilding my 4.7-stdthread, as they suffer from the >>>>> same issues. The 4.6.3-1-release i686-win32 toolchain works fine, it would >>>>> only be the Linux toolchains that are fixed for that. >>>>> >>>>> If GCC 4.7.2 is released tomorrow, I'm going to ... well... get myself >>>>> drunk. No... I'll just bravely build the new release ASAP. >>>>> >>>>> If there are still issues, I'd love to hear about them. >>>>> >>>>> Enjoy, >>>>> >>>>> Ruben >>>>> >>>>> PS: Download links are still in the same place as last time: >>>>> >>>>> https://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Personal%20Builds/rubenvb/release/ >>>>> >>>>> https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/gcc-4.7-release/ >>>>> >>>>> https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/gcc-4.7-release/ >>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards >>>> Yuchen >>>> >>> >> > > > > -- > Best Regards > Yuchen > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |