To: Nigel Stephens <nigel AT algor DOT co DOT uk>
Cc: "Christoph P. Kukulies" <kuku AT gilberto DOT physik DOT rwth-aachen DOT de>,
        djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: cross compiling
Date: Thu, 9 Mar 1995 07:10:28 PST
From: Marty Leisner <leisner AT sdsp DOT mc DOT xerox DOT com>


> 3) Configure each of gcc and binutils by using:
> 	./configure --host=i386-bsd --target=i386-go32
> 
>    (It may be that some of the go32 config files are missing, in which
>     case I've got working copies, let me know what's missing).
>  

Why do you have to make gcc?  I just use (on linux) my base gcc (I have
a problem with {var,std}arg.h with gcc 2.5.8...

I have a script I run which just does (this is from memory)

#! /bin/bash

djgpp=/dos/marty/gnu

export LIBRARY_PATH=$djgpp/lib
include=$djgpp/include
export LDEMULATION=i386go32
#export GCC_EXEC_PREFIX=/u/marty/binutils/bin/go32
#exec gcc -nostdinc -idirafter /dos/gnu/include   $* 
exec gcc -idirafter $include -nostdinc ${1+"$@"}


After some understanding (and working with this) I think you just need
binary tools with support i386go32...It seems you can even
use the native assembler for this...

For the last few days I've been using i386coff
(since the new binutils are distributed that
way and I'm not making them) and djgcc programs
seem (?? they bomb on exit) to run...

At least in dosemu on linux...

marty
leisner AT sdsp DOT mc DOT xerox DOT com  
Member of the League for Programming Freedom