This is the mail archive of the
mailing list for the GCC project.
RE: [PATCH] Add --with-cross configure option to force -DCROSS_COMPILE behavior
- From: Dan Kegel <dkegel at ixiacom dot com>
- To: 'Daniel Jacobowitz ' <drow at mvista dot com>, 'DJ Delorie ' <dj at redhat dot com>
- Cc: Dan Kegel <dkegel at ixiacom dot com>, "'gcc-patches at gcc dot gnu dot org '" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 3 Jun 2003 13:06:37 -0700
- Subject: RE: [PATCH] Add --with-cross configure option to force -DCROSS_COMPILE behavior
The sysroot patches look completely orthogonal to this issue.
I looked at them, and they have seem to no effect on whether a
cross-compiler is built. I'm a bit confused about how they relate to this
If you say playing with --host and --target can do the job, ok,
I'll go give that a shot.
From: Daniel Jacobowitz
To: DJ Delorie
Cc: firstname.lastname@example.org; email@example.com
Sent: 02.06.2003 18:30
Subject: Re: [PATCH] Add --with-cross configure option to force
On Mon, Jun 02, 2003 at 09:03:59PM -0400, DJ Delorie wrote:
> Isn't this what the sysroot patches were for?
Yes, absolutely. That should be used instead. It does require that
$build != $target, but:
> Note that you can also tweak the --host parameter in subtle ways, like
> "--host=i386-pc-linux --target=i686-pc-linux"
Or even subtler:
MontaVista Software Debian GNU/Linux Developer