From: Paul <ele...@ya...> - 2008-01-20 23:52:16
|
On 19/01/2008, Keith Marshall <kei...@us...> wrote: snip > > But, why even bother to add yet another `assume' for TARGET_CPU, in the > config file; just define whatever you want on the command line: > > sh x86-mingw32-build.sh [--options] TARGET_CPU=i686 i686-pc-mingw32 > > (or whatever else you prefer), should do the trick. Hi Keith, The command line options would certainly be more convenient ... if they worked. A simple patch for demonstrating my problem: --- x86-mingw32-build.sh-orig 2006-11-06 07:26:39.000000000 +0800 +++ x86-mingw32-build.sh 2008-01-21 08:45:31.648764605 +0900 @@ -33,6 +33,13 @@ TARGET=${1-${TARGET-"${TARGET_CPU-i386}-mingw32"}} +echo $PACKAGE_DIR +echo $PATCHES_DIR +echo $TARGET +echo $CFLAGS_FOR_RUNTIME + +exit 0 + assume BUILD_METHOD interactive test "$BUILD_METHOD" = interactive && BUILD_METHOD=dialogue || BUILD_METHOD=batch test -r $script.$BUILD_METHOD && . $script.$BUILD_METHOD now try running this: ./x86-mingw32-build.sh --unattended --no-download PACKAGE_DIR=/tmp/packages TARGET=i686 and you will see this: PACKAGE_DIR=/tmp/packages /home/paul/packages/mingw-3.4.5/patches TARGET=i686 -O2 -mms-bitfields -march=i386 this seems to imply that PACKAGE_DIR="PACKAGE_DIR=/tmp/packages" Also, it should be looking for patches in /tmp/packages/patches, And I thought that -march should ideally be =i686 ? thanks, Paul |