From: Dave K. <dav...@ar...> - 2008-07-29 17:15:56
|
Keith Marshall wrote on 13 December 2007 20:14: [ Yeh, it was a while ago. So I have more info now, because I've actually been trying the mingw.org scripts for the first time. ] > On Thu, 2007-12-13 at 19:50 +0000, Dave Korn wrote: >>> How do you do this. Sorry for the dumb question. I >>> couldnt really find any documentation. I would like to >>> try building some programs on linux for windows. >> >> The simplest way I know is to go to >> >> http://www.profv.de/mingw_cross_env/ > > What is wrong with the cross-compiler build scripts which we ourselves > provide? What, like apart from it not working? ;-) > Use somebody else's, and you'll likely find you are on your own. I'll file a bug, but just in case this rings a bell with anyone: the build failed when trying to configure w32api with a file-not-found error. ------------------<snip>------------------ make[2]: Nothing to be done for `install'. make[2]: Leaving directory `/home/dk/mingw/tmp/mingw-3.4.5/build-gcc/libiberty/testsuite' make[1]: Leaving directory `/home/dk/mingw/tmp/mingw-3.4.5/build-gcc/libiberty' x86-mingw32-build.sh: stage 1: build w32api ... x86-mingw32-build.sh: line 139: ../config.guess: No such file or directory x86-mingw32-build.sh: line 139: ../configure: No such file or directory x86-mingw32-build.sh: unrecoverable error configuring w32api ------------------<snip>------------------ and this turns out because something went wrong with the temp build dir structure, which made this code here rather unhappy: ------------------<snip>------------------ 137 case $COMPONENT in mingw-runtime | w32api) 138 setbuilddir ${COMPONENT}-* 139 $RUN ../configure --prefix="$INSTALL_DIR" --host="$TARGET" \ 140 --build=${BUILD_PLATFORM=`../config.guess`} || die $? \ 141 "$unrecoverable configuring $COMPONENT" ------------------<snip>------------------ Now, I guess that line 138 is trying to use a wildcard to cd into whatever is the component directory without having to care about the trailing version-number suffix, but it doesn't work nicely for me because looking in the build temp dir: [dk@quattro x86-mingw32-build.sh-0.0-20061107-1]$ ls -la ../tmp/mingw-3.4.5/ total 32 drwxr-xr-x 8 dk eng 4096 Jul 29 16:57 . drwxr-xr-x 3 dk eng 4096 Jul 29 16:52 .. drwx------ 18 dk eng 4096 Jul 29 16:55 binutils-2.17.50-20060716-1-src drwxr-xr-x 5 dk eng 4096 Jul 29 16:58 build-gcc drwxr-xr-x 10 dk eng 4096 Dec 12 2005 gcc-3.4.5-20060117-1 drwxr-xr-x 5 dk eng 4096 Aug 30 2006 mingw-runtime-3.10 drwxr-xr-x 4 dk eng 4096 Jul 29 17:00 w32api-* drwxr-xr-x 4 dk eng 4096 Apr 14 2006 w32api-3.7 [dk@quattro x86-mingw32-build.sh-0.0-20061107-1]$ .... it looks like the directory actually got created! Anyway, if anyone's already discovered this one, please let us know how you fixed it. I tried googling this but couldn't find anything similar, so in the meanwhile I'll get on with filing a bug in the tracker. cheers, DaveK -- Can't think of a witty .sigline today.... |