Alexey Pavlov [mailto:[email protected]] wrote:
]> 14 окт. 2014 г., в 21:26, Scott Duplichan <[email protected]> написал(а): ]> ]> Alexey Pavlov [mailto:[email protected]] wrote: ]> ]> ]12 окт. 2014 г., в 8:28, Scott Duplichan <[email protected]> написал(а): ]> ] ]> ]> Hello, ]> ]> ]> ]> I am trying to make a gcc 4.8.1 cross compiler for coreboot. ]> ]> I get a fail due to missing wait.h and resource.h. Fixincl.c ]> ]> needs functions wait, fork, and pipe, apparently. Are these ]> ]> available for msys2? Or is there some other way to get around ]> ]> this problem? ]> ]> ]> ]Headers wait.h and resource.h are present in msys2-runtime-devel package. But we can’t say more while you not ]told steps that ]you do for building cross compiler. ]> ]> Thanks for this information. I found the real cause of my gcc build failure. ]> Building from mingw32_shell worked but building from mingw64_shell failed. ]> The cause is this code in fixincludes\configure.ac: ]> ]> # Choose one or two-process fix methodology. Systems that cannot handle ]> # bi-directional pipes must use the two process method. ]> # ]> AC_ARG_ENABLE([twoprocess], ]> [ --enable-twoprocess Use a separate process to apply the fixes], ]> [if test "x$enable_twoprocess" = xyes; then ]> TARGET=twoprocess ]> else ]> TARGET=oneprocess ]> fi], ]> [case $host in ]> i?86-*-msdosdjgpp* | \ ]> i?86-*-mingw32* | \ ]> x86_64-*-mingw32* | \ ]> *-*-beos* | \ ]> *-*-*vms*) ]> TARGET=twoprocess ]> ;; ]> ]> * ) ]> TARGET=oneprocess ]> ;; ]> esac]) ]> ]> ]> Apparently the code wants to enable a feature to make fixincludes run ]> faster. But the feature relies on bi-directional fork(), wait() and ]> bi-directional pipes. The feature is automatically disabled for certain ]> hosts, such as msdosdjgpp and mingw32. But mingw64 is not in the list, ]> so it tries to use these features. The simple work-around is to add gcc ]> configure option --enable-twoprocess. When I add this option, the 64-bit ]> build works the same as the 32-bit build. ] ]mingw64 is in list already. see: ]> x86_64-*-mingw32* | \ Yes it is. But I think the '-ming32' part doesn't match when configure is run from the 64-bit shell: $ ./configure checking build system type... x86_64-pc-mingw64 checking host system type... x86_64-pc-mingw64 checking target system type... x86_64-pc-mingw64 It is not clear to me how configure constructs the name x86_64-pc-mingw64, but apparently the last part is from the uname command. Thanks, Scott ]Regards, ]Alexey. ] ]> ]> Thanks, ]> Scott ]> ]> ]> ]Regards, ]> ]Alexey. ]> ] ]> ]> Thanks, ]> ]> Scott ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
