The cross compile patch is similar to what I did for
Guile and has
still some bits from Daniel Goertzen's

   
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1006238&group_id=5470

The mingw patch is based on Matthias Kramm's

   
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1053879&group_id=5470

but adds autoconf tests and does have his C modifications.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond -
The music typesetter
http://www.xs4all.nl/~jantien       |
http://www.lilypond.org

Logged In: YES 
user_id=1368960

.... and does NOT have his C modifications
 

Logged In: YES 
user_id=1368960

The second mingw patch actually produces a working python,
fixing
   * loadable dll modules
   * argv0 relocation
   * posixflavour nt

-- Jan.

Logged In: YES 
user_id=1417949

Hi, I patched Python 2.4.2 source code download with this 
(can't get CVS as bandwidth is limited).

context-cross.patch fails on one chunk of Makefile.pre.in, 
although hand application fixed it.  Otherwise, context-
mingw-2.patch applied cleanly.

With both applied, I did the following:

export BASECFLAGS="-mcpu=arm9tdmi -mcpu=arm9tdmi -ffast-
math -mthumb -mthumb-interwork -DARM9 -D__NDS__"
export CFLAGS="-mcpu=arm9tdmi -mcpu=arm9tdmi -ffast-math -
mthumb -mthumb-interwork -DARM9  -D__NDS__"
export LDFLAGS="-specs=ds_arm9.specs -g -mthumb -mthumb-
interwork -Wl,-Map,libpython2.4.map"

sh configure --host=arm-elf

This is what eventually happened:

PATH=/usr/bin:.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/s
ystem32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program 
Files/ATI Technologies/ATI Control 
Panel:/c/PROGRA~1/COMMON~1/SONICS~1/:/c/Program 
Files/Common 
Files/Adobe/AGL:/usr/bin:/c/devkitpro/devkitarm/bin:. cc -
c -I -I./Include  -o Parser/acceler.x Parser/acceler.c
/bin/sh: Files/ATI: No such file or directory
make: *** [Parser/acceler.x] Error 127

Looks like the patch needs to handle paths with spaces in, 
in the PATH.

Logged In: YES 
user_id=1368960

> Looks like the patch needs to handle paths with spaces in, 
> in the PATH.

Why do you think that?  You will find that no autotooled
package will build or install in directories with spaces.

If this would be possible at all, it would be a separate
feature.  I do not see a dependency with cross compilation
or mingw building.

Logged In: YES 
user_id=1417949

> Why do you think that?  You will find that no autotooled
> package will build or install in directories with spaces

Perhaps I was not clear enough.  The problem is not that I 
am building in those directories, it is that the patch 
sets the PATH environment variable as a prefix to the 
compilation command (in the same line).  And on Windows, 
it is not uncommon for directories in Program Files and 
other directories with spaces in their names to be in the 
path.  This breaks the correctness of the command line and 
the execution of it.

Take another look at the erroneous command:

PATH=/usr/bin:.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/s
ystem32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/Program 
Files/ATI Technologies/ATI Control 
Panel:/c/PROGRA~1/COMMON~1/SONICS~1/:/c/Program 
Files/Common 
Files/Adobe/AGL:/usr/bin:/c/devkitpro/devkitarm/bin:. cc -
c -I -I./Include  -o Parser/acceler.x Parser/acceler.c

And the error:

/bin/sh: Files/ATI: No such file or directory
make: *** [Parser/acceler.x] Error 127

Hope this helps.

superseded by #1597850

superseded by #1597850